On 18/03/2011 09:14, Andy Wokula wrote:
Am 14.03.2011 19:46, schrieb Gary Johnson:
I've encountered a problem using gvim 7.3.138 on a Windows XP system
because of the way that Vim expands "plugin/**/*.vim" when it loads
plugins. Specifically, Vim includes RCS file names that end with
.vim,v in that expansion.
The error can also be observed by cd'ing to an RCS directory
containing one or more files ending in ".vim,v" and executing from
within Vim
:args *.vim
Vim will put all the *.vim,v files in the argument list and open the
first one.
This error does not occur on Unix systems, including HP-UX, Solaris
and Linux.
The gvim for Windows I was using was the latest without-Cream
version available from the Cream web site, 7.3.138.
Looks like it's not specific to Vim, the dir command in WinXP does the
same:
C:\temp>dir *.vim
finds, for example, the file "abc.vim,def".
The Win32 file search functions search both the long and short versions
of file names. When the short version of a file name is created any
extension is limited to 3 characters. You can see this when you do a
dir /x in a directory. See also:
http://blogs.msdn.com/b/oldnewthing/archive/2005/07/20/440918.aspx
There are ...Ex() versions of the file search functions which on
Win2008R2 and Win7 can ignore the short file names but that doesn't help
with VIM on older versions of Windows.
Mike
--
How do you know when you have run out of invisible ink?
--
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
