Error running Windows gvim.exe from Cygwin
Gary Johnson
$ /cygdrive/c/Program\ Files/Vim/vim73f/gvim.exe
but when I try to run Vim 7.3.2 from a Cygwin 1.7 bash prompt the
same way, i.e.,
$ /cygdrive/c/Program\ Files/Vim/vim73/gvim.exe
I get a DOS window with "C:\Program Files\Vim\vim73\vimrun.exe" in
the title bar and this text in the window:
/bin/bash /c <symlink>�/
The system cannot find the file specified.
shell returned 1
Hit any key to close this window...
When I hit Enter, a pop-up window from Vim appears, titled "Message"
and containing this text:
:!<symlink>**/*
and an "Ok" button, where the first * is actually a y with an
umlaut, the second * is some character that looks like a b and a p
sharing the same circle part, and the third * is an open square.
I can test the Cygwin 1.5 / Vim 7.3.2 combination a little later.
Can anyone tell me what's going on and how it can be fixed?
Regards,
Gary
Gary Johnson
Update:
I noticed that when gvim 7.3.2 finally came up, none of the settings
in my vimrc had been applied even though :scriptnames said ~/.vimrc
had been read.
I think this may be a PEBKAC.
Each of the three PCs on which I use Cygwin has a slightly different
Cygwin configuration, primarily different versions of Cygwin and
different locations for $HOME. In short, on some of the systems,
executing gvim.exe from the Cygwin shell causes gvim.exe to try to
read a ~/.vimrc that is a Cygwin symlink. Gvim 7.3f silently fails
to read ~/.vimrc, whereas gvim 7.3.2 throws the error message
described above. Executing gvim like this works.
( unset HOME; /cygdrive/c/Program\ Files/Vim/vim73/gvim.exe; )
Now I just need to figure out if that's the solution I want.
Regards,
Gary
Tony Mechelynck
I don't know the answer to your problem, but...
� (Latin small letter y with diaeresis) is 0xFF
� ("a b and p sharing the same circle part") is the Latin letter thorn,
used in Modern Icelandic and in several former states of Germanic
languages including Old English, to represent the unvoiced th sound as
in thin. Its hex value is 0xFE
0xFF 0xFE is the hex representation of a UTF-16le BOM (Unicode U+FEFF),
something often used at the very start of a Unicode file in order to
signal that it is recorded in little-endian UTF-16. This said, I still
don't know what to do, unless maybe refraining from running from a
Cygwin bash shell a Vim executable built for Native Windows (with no
runtime requirement for the cygwin1.dll)
Best regards,
Tony.
--
God rest ye CS students now,
Let nothing you dismay.
The VAX is down and won't be up,
Until the first of May.
The program that was due this morn,
Won't be postponed, they say.
Oh, tidings of comfort and joy,
Comfort and joy,
Oh, tidings of comfort and joy.
The bearings on the drum are gone,
The disk is wobbling, too.
We've found a bug in Lisp, and Algol
Can't tell false from true.
And now we find that we can't get
At Berkeley's 4.2.
(chorus)
igor.mikushkin
source C:\\Documents\ and\ Settings\\yourname\\My\
Documents\\Dropbox\\Personal\\home\\.vimrc
You can use it instead of symlimk.
Igor
--
View this message in context: http://vim.1045645.n5.nabble.com/Error-running-Windows-gvim-exe-from-Cygwin-tp2728941p4267589.html
Sent from the Vim - General mailing list archive at Nabble.com.