Albie Janse van Rensburg wrote:
Steve Hall wrote:
From: Albie Janse van Rensburg, Fri, May 04, 2007 6:35 am
I recently decided to try out the Cream build (sans Cream) of Vim,
with all the new patches (from
http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721).
Now, I seem to be unable to edit my vimrc without bringing Vim to a
complete halt!
Sound like the age-old and infamous TCL with Cygwin problem:
http://tech.groups.yahoo.com/group/vim/message/78505
http://tech.groups.yahoo.com/group/vim/message/78506 (solution)
Yep, that's it. I should have mentioned I am using cygwin, I guess.
Why does this bug appear on the patched version of Vim, but not the
unpatched v7.0?
Thanks for the pointer.
Another workaround is never to use from Cygwin bash a Vim binary for
native-Windows (and never use Vim-for-Cygwin except from within Cygwin). If
your Cygwin /bin and /usr/bin aren't in the non-Cygwin PATH, then
Vim-for-Windows will find TCL-for-Windows. Since they are added in front at
Cygwin bash startup, Vim-for-Cygwin will find TCL-for-Cygwin first.
(Vim-for-Windows will, for instance, be vim.exe and gvim.exe from the
directory C:\Program Files\Vim\vim70, which is their $VIMRUNTIME.
Vim-for-Cygwin will be, for instance, /usr/bin/vim.exe with its $VIMRUNTIME at
/usr/share/vim/vim70/.)
Vhy isn't it present in Bram's 7.0.000? Err... isn't the latter compiled
without TCL support? Then it never looks for a TCL dll.
Best regards,
Tony.
--
Frobnitz, pl. Frobnitzem (frob'nitsm) n.:
An unspecified physical object, a widget. Also refers to
electronic black boxes. This rare form is usually abbreviated to
FROTZ, or more commonly to FROB. Also used are FROBNULE, FROBULE, and
FROBNODULE. Starting perhaps in 1979, FROBBOZ (fruh-bahz'), pl.
FROBBOTZIM, has also become very popular, largely due to its exposure
via the Adventure spin-off called Zork (Dungeon). These can also be
applied to non-physical objects, such as data structures.
