> I haven't had much trouble with filenames personally, as long as I stick
> to forward slashes (which work on Windows) instead of backslashes (which
> don't work on anything but Windows) and don't mangle user-provided
> pathnames starting with drive letters on Windows. Could you be more
> specific in what can go wrong?!
The problem occurs when using full/absolute filenames or when e.g. (on
windows) the current working directory is on a different drive than
the current buffer so that expand('%') expands to an absolute
filename. You could circumvent this problem by temporarily chdir'ing
into the buffer's directory but this could cause problems when the
executable expects the cwd to be, e.g., a project's root directory
etc.
Quite a few plugins don't work properly when you use e.g. windows gvim
with cygwin tools. Since hardly anybody mentions similar problems on
this list, I'd assume though that only very few people are affected by
this problem.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
