1
1
I'm using the Cream version of gVim, and i'd like to make an alias to open files from a Cygwin shell in Cream. Running the gVim executable from Cygwin gives the following error (in a Windows cmd
window) :
/bin/zsh /c <symlink> ■c
The system cannot find the file specified.
shell returned 1
Hit any key to close this window..
.
Thanks, but it still gives the same error. I did notice one thing though: when I close the
cmd
window, there's a gVIM dialog box underneath with a single button with the message:!<symlink>ÿþc
. It suppose it has something to do with the fact thatgvim.exe
is actually a Windows symlink and that Cygwin can't properly handle it. When I click on it gVIM works fine but it's still an annoyance... – Andrei – 2010-08-24T13:22:18.720That used to work. I just got back to my Cygwin 1.7 system which has a fresh install of Vim from the Cream site and verified the behavior you're seeing. I'll look into it. – garyjohn – 2010-08-26T16:19:25.907
1The system on which this worked for me has a ~/_vimrc shared by both Windows gvim and Cygwin vim. The system on which this fails has a $HOME/.vimrc that is a Cygwin symlink to the regular file $HOMEDRIVE/$HOMEDIR/_vimrc. I "fixed" the problem by invoking gvim.exe like this:
( unset HOME; /cygdrive/c/Program\ Files\Vim/vim73/gvim.exe; )
, which caused gvim.exe to read the real file instead of the symlink. So the problem could be as you said thatgvim.exe
is a Windows symlink or that your ~/.vimrc is a Cygwin symlink. I didn't try Luc's suggestion. – garyjohn – 2010-08-26T18:37:57.530