2008/12/4 fritzophrenic <[EMAIL PROTECTED]>: > On Dec 3, 7:47 pm, "Yongwei Wu" <[EMAIL PROTECTED]> wrote: >> When I have :set ffs=unix,dos in >> _vimrc, the empty file on opening vim, or results of :enew, still has >> ff=dos on Windows. >> >> I even tried putting set ffs=unix,dos in a test.vim, and started vim >> with gvim -u test.vim --noplugin, and the result was still the same: >> ff=dos. Putting in set ff=unix has effects. > > That's bizarre. What about the output of ":verbose set ffs?" in both > cases?
Path to my test.vim. > I don't think it should matter, but: > > "Using the '-u' argument has the side effect that the 'compatible' > option will be on by default." (:help -u) Adding :set nocompatible in test.vim makes no difference. > Maybe you are setting 'nocompatible' somewhere after you set the ffs > value, resetting it to the default? And it does not matter, since I checked the value of ffs in vim. >> I really can't imagine why it works for you. >> > And I can't imagine why it doesn't for you :-) Strictly speaking, my results make more sense. Vim help file does not say that the first value in ffs will be used as the default encoding. On the contrary, I know that setting the value of fenc will affect the encoding of the empty file. And it does not persist, since neither fenc nor ff is really 'global': Vim help states clearly that they are local to buffer. >> I am using gvim 7.2.60 on Windows XP. >> > > Me, too. The 'cream' compile from sourceforge. I use my own build (executables only), available at: http://wyw.dcweb.cn/download.asp?path=vim&file=gvim72.zip You may have a try, but I do not think it can make a difference. I would rather think your environment affected. Did you try with -u test.vim, as I did? Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/ --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
