Ok, I’ve found something that works. Associating a batch file as Vladimir suggested didn’t work, but the bash arguments were key. Short and sweet: associate with this command: “C:\cygwin\bin\bash.exe” -li “%1” %* Long version if you don’t know how: In Explorer, go to Tools/Folder Options/File Types. I already had an SH entry for Bash Script. … Read more
Ctrl+w and right and left arrow can be used to move between any split windows on vim, not only vimdiff splits. These keys do work here on cygwin; also, Ctrl+w w also moves to the next window, but without the delay you mentioned. It is possible that you have mapped these keys in your .vimrc … Read more
uname -m And it should say x86_64 in the output if it’s 64-bit, or i686 if 32-bit.
search for /usr/share/automake*/config.guess check the latest version of automake $ which automake $ automake –version find the appropriate automake folder in /usr/share/automake.1.11.1/config.guess replace config.guess from your build tree with /usr/share/automake.1.11.1/config.guess (The same may/is usually needed for config.sub.)
./a.exe at the prompt
When you run the Cygwin installer again to install new packages, you might notice that searching for “scp” produces no results. It’s actually part of the “openssh” package.
As far as I know, it is not possible to do what you want. I see this as a bug in bash’s history processing that could be improved. export HISTCONTROL=ignoreboth:erasedups # no duplicate entries shopt -s histappend # append history file export PROMPT_COMMAND=”history -a” # update histfile after every command This will keep the in … Read more
This error message means that Windows isn’t able to find “cygwin1.dll”. The Programs that the Cygwin gcc create depend on this DLL. The file is part of cygwin , so most likely it’s located in C:\cygwin\bin. To fix the problem all you have to do is add C:\cygwin\bin (or the location where cygwin1.dll can be … Read more
The error is because your gcc-core package and gcc-g++ are not of the same version. Either downgrade one of them to solve the problem or update both the libraries. Updating both the libraries is the recommended way.
Using the | character without escaping it in a basic regular expression will only match the | literal. For instance, if you have a file with contents string1 string2 string1|string2 Using grep “string1|string2” my.file will only match the last line $ grep “string1|string2” my.file string1|string2 In order to use the alternation operator |, you could: … Read more