On 04/12/08 15:03, fritzophrenic wrote:
>
>
> 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?
>
> 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)
>
> Maybe you are setting 'nocompatible' somewhere after you set the ffs
> value, resetting it to the default?
>
>> I really can't imagine why it works for you.
>>
>
> And I can't imagine why it doesn't for you :-)
>
>> I am using gvim 7.2.60 on Windows XP.
>>
>
> Me, too. The 'cream' compile from sourceforge.
If you want to start Vim with standard startup scripts, it is also possible:
cd "C:\Program Files\vim\vim72"
.\gvim -u vimrc_example.vim
starts with a standard vimrc which sets 'nocompatible'. It also loads
all global plugins.
gvim -u NORC -N
starts gvim with plugins but no vimrc, in 'nocompatible' mode.
gvim -u NONE -N
starts gvim in 'nocompatible' mode with no vimrc and no plugins.
gvim -u test.vim --noplugin
starts with no plugins and test.vim as the only vimrc. 'compatible' will
be on unless and until test.vim sets 'nocompatible'.
And so on.
I'm using an own-compiled gvim 7.2.64 with GTK2 GUI on openSUSE Linux,
so I don't think my results are easily comparable with yours what
concerns platform-dependent options like 'ff' and 'ffs'.
Best regards,
Tony.
--
It's the thought, if any, that counts!
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
