On 23 Oct 2012, at 03:42, Tony Mechelynck wrote: > On 12/07/12 18:06, Andrew Long wrote: >> >> >> Begin forwarded message: >> >>> From: "Long, Andrew" <[email protected]> >>> Subject: Vim under cygwin >>> Date: 12 July 2012 10:18:32 GMT+01:00 >>> To: [email protected] >>> >>> >>> 0126792@XP037234 ~/NRock/Projects/dbJnlStats/working >>> $ vim -gS Session.vim >>> cygwin warning: >>> MS-DOS style path detected: C:\winnt\profiles\0126792\vimfiles\plugin >>> Preferred POSIX equivalent is: /home/0126792/vimfiles/plugin >>> CYGWIN environment variable option "nodosfilewarning" turns off this >>> warning. >>> Consult the user's guide for more details about POSIX paths: >>> http://cygwin.com/cygwin-ug-net/using.html#using-pathnames >>> >>> 0126792@XP037234 ~/NRock/Projects/dbJnlStats/working >>> >>> -- >>> Andrew Long IT Specialist >>> Mainframe Management Virgin Money >>> +44 (191) 279 4537 Andrew dot Long at Virgin Money dot com >>> >>> <snip/> >> >> The message above (sometimes) comes out of a fresh XTerm session when I >> start vim using a saved Session.vim file. I've tried to locate the offending >> file using egrep on all the .vim files in my vimfiles folder (which has a >> soft link of '.vim' pointing at it!)also in the Session.vim file, but no >> matches. >> >> It doesn't seem to cause any real problems, but it's a message I'd like to >> get rid of. Any suggestions as to how I can find the problem and put it >> right, please? >> >> Regards, Andy >> > > This message might happen if you use the same Session.vim with a > native-Windows Vim (compiled to run in Windows without Cygwin, for instance > Steve Hall's "Vim without Cream") and with a Cygwin version of Vim (compiled > to use the Cygwin DLL, for instance the console Vim distributed with Cygwin) > and if both of them use :mksession (for instance at shutdown). Then the > native-Windows Vim will probably write a Windows-like path (with backslashes) > which the Cygwin Vim won't like.
I no longer have a native windows vim installed on my system at work - I uninstalled it many years ago and have stuck with cygwin ever since. > > If that string is in none of your *.vim files, it might be in a "system > vimrc" provided by Cygwin (see near the middle of the output of the :version > command of your Cygwin Vim to know where it is — $VIM/vimrc is the default, > but /etc/vimrc is often set instead at compile-time, in both cases normally > with no initial dot in the filename) or in a vim.bat wrapper if you have one > in your $PATH, or if none of these match, in some custom change brought by > the Cygwin engineers into the Vim C source. (The "system vimrc" case seems > most likely to me.) I haven't yet looked in all of the *.vim files. I don't have a system vimrc file at $VIM, thogh there is a vimrc_sample in $VIM/vim73 ($VIM points at /usr/share/vim) I think the path must be constructed somehow, as it's inheriting the path to my $HOME directory (either in a POSIX or Windows style) and then putting the terminal name of the .vim/vimfiles folder in front of 'plugin'; I only hear about it when it's using the Windows form of the path. If I get a chance before I go on holiday next week I'll try to find the place in my local or system *.vim files. Regards, Andy -- Andrew Long andrew dot long at mac dot com -- You received this message from the "vim_use" 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
