pe plugin on"
> > and surrounding all vim-features with
> >
> > if v:progname != "vi"
> > s00perd00per vim/gvim options
> > endif
>
> Bad idea, i don't like typing m after vi to get the editor.
That's OK, you can edit the conffile.
Hamish
--
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Submitted 21-Jan-02 by Hans Freitag:
>> if v:progname != "vi"
>> s00perd00per vim/gvim options
>> endif
>
> Bad idea, i don't like typing m after vi to get the editor.
This is a much more efficient solution than what some other distros have
done: splitting vim into vim-{common,minimal,enhanc
lly annoying "filetype plugin on"
>> and surrounding all vim-features with
>>
>> if v:progname != "vi"
>> s00perd00per vim/gvim options
>> endif
>
>Bad idea, i don't like typing m after vi to get the editor.
But that's exactly the point. If I type 'vi' I want to get the *the* editor.
And that is 'vi'. Not 'vim'.
Mike.
Hi,
On Sun, Jan 20, 2002 at 12:09:10PM +, Miquel van Smoorenburg wrote:
> How about turning off all non-standard-vi features by default
> such as "autoindent" and the especially annoying "filetype plugin on"
> and surrounding all vim-features w
a vimrc file with lines commented out that
>the user can enable. Note that this is the strategy for bash.
How about turning off all non-standard-vi features by default
such as "autoindent" and the especially annoying "filetype plugin on"
and surrounding all vim-features with
Wichert Akkerman declaimed:
> Previously Paul Mackinney wrote:
> > What would be helpful is a README.Debian file in /usr/doc/vim that
> > alerts the user to the existence of /etc/vim/vimrc and its nice set of
> > potential customizations. I had overlooked the vim stuff in /etc, but I
> > have lea
Previously Paul Mackinney wrote:
> What would be helpful is a README.Debian file in /usr/doc/vim that
> alerts the user to the existence of /etc/vim/vimrc and its nice set of
> potential customizations. I had overlooked the vim stuff in /etc, but I
> have learned to check the /usr/doc directory.
Wichert Akkerman declaimed:
> Previously Caleb Shay wrote:
> > I second this. For example, at the bottom of /etc/vim/vimrc there are
> > several lines commented out "as they cause vim to behave a lot different
> > from regular vi". However, as was pointed out below, vim is NOT the
> > default vi
Previously Caleb Shay wrote:
> I second this. For example, at the bottom of /etc/vim/vimrc there are
> several lines commented out "as they cause vim to behave a lot different
> from regular vi". However, as was pointed out below, vim is NOT the
> default vi when you install, so why not enable so
Hello,
I would like to see more user feedback on Debian's settings of the
VIM editor. Currently, two important features are disabled in the
default configurations: Syntax highlighting and special intending
schemes. The question is: why?
Some (influent) people want to make VIM behave as the "normal
10 matches
Mail list logo