Martin Stubenschrott wrote:
On Fri, Jan 19, 2007 at 07:28:51PM +1100, John Beckett wrote:
In the BOF talk, Bram really was asking for ideas on what would make
new users flock to Vim.
Biggest changes would really be defaults imho. And that should be done
without really compromising compatible mode.
First and most important thing would be to enable nocompatible by
default when the executable name is (g)vim, compatible should still be
on, when the executable name is vi. Enabling/disabling by an (non-)existing
.vimrc file is not the right way, because if you make your own .vimrc
file, you want to add some usefull behavior and in exchange you get less
optimal behavior in many cases, and probably don't know why that is
happening, just because you created a .vimrc with some mappings.
It's really crazy that you can't even press Tab after :e to complete
filenames in compatible mode.
Remember: vi used to have, not a vimrc but an exrc. If your settings file is
called exrc, Vim won't set 'nocompatible'.
Second would be to enable :syntax on by default in nocompatible mode.
Every bullshit-editor (sorry for the word), has syntax highlighting now,
and even a Pentium 200 should be fast enough to deal with syntax
highligthing.
Third, I would enable isearch by default, but keep hlsearch off (as it
is now).
Most other options are right for experts and newbies as well, or at
least have another reason for their default setting.
--
Martin
I would leave the defaults as they are. The vimrc_example.vim already sets
"filetype plugin indent on" and "syntax on", BTW. Sourcing that script from
your vimrc is IMHO no great hassle, and gives the benefit of many "better"
settings, not only syntax highlights but e.g. going back to the latest edit
position whenever you enter a file.
IIUC, there _are_ vimrc scripts out there (I'd guess there are many of them)
which don't bother to explicitly set any settings to what is currently their
default. Changing such defaults would break those scripts.
Best regards,
Tony.
