Re: VIM features
On Mon, Jan 21, 2002 at 09:52:10AM +0100, Hans Freitag wrote: 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 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]
Re: VIM features
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 with if v:progname != vi s00perd00per vim/gvim options endif Bad idea, i don't like typing m after vi to get the editor. I did this on my workstation, if I call vim as vi I get the bog-standard vi, if I call it as vim I get color, syntax higlighting, autoindent, filetype plugin on, viminfo, showcmd, autowrite, etc etc Maybe we could make 2 or more different example configurations, and put them into /usr/doc/vim. bye -- May the source be with you!
Re: VIM features
In article [EMAIL PROTECTED], Hans Freitag [EMAIL PROTECTED] wrote: 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 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.
Re: VIM features
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,enhanced} in which -minimal
closely emulates vi (and is named such) and resides in /bin and
-enhanced uses all the bells and whistles. I agree that vi should be
vi-like without unexpected vim-like behaviors.
--
Anton GrahamGPG ID: 0x18F78541
[EMAIL PROTECTED]
Do not meddle in the affairs of the undead, for you are crunchy and good
with ketchup.
pgp856Zhog8nf.pgp
Description: PGP signature
Re: VIM features
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 learned to check the /usr/doc directory. Feel free to write one :) Wichet. Touche! What I was thinking of is this simple, proposed pathname /usr/doc/vim/README.Debian. header Administrators are encouraged to review the default configuration files /etc/vim/gvimrc and /etc/vim/vimrc. These contain useful examples and instructions for globally enabling some of Vim's non-vi features such as syntax highlighting and automatic saves. footer HTH, Paul -- Paul Mackinney | Another look at Sept 11 [EMAIL PROTECTED] | http://www.copvcia.com/
Re: VIM features
In article [EMAIL PROTECTED], Paul Mackinney [EMAIL PROTECTED] wrote: 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 when you install, so why not enable some more of it's better features. Because I'm not willing to for several reasons: 1. every time I enable a feature that makes vim a bit more unlike vi I get multiple bugreports 2. vim is very well documented, if people want to try any of its features they can trivially enable them themselves 3. which features you want enabled is a very personal choice, one that I am not willing to make for users. So I'll always pick the choice that makes vim more like stock vi. This keeps things consistent and prevents endless debates. I don't at all mind having 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 if v:progname != vi s00perd00per vim/gvim options endif I did this on my workstation, if I call vim as vi I get the bog-standard vi, if I call it as vim I get color, syntax higlighting, autoindent, filetype plugin on, viminfo, showcmd, autowrite, etc etc IMO this is the right solution Mike.
Re: VIM features
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 when you install, so why not enable some more of it's better features. Because I'm not willing to for several reasons: 1. every time I enable a feature that makes vim a bit more unlike vi I get multiple bugreports 2. vim is very well documented, if people want to try any of its features they can trivially enable them themselves 3. which features you want enabled is a very personal choice, one that I am not willing to make for users. So I'll always pick the choice that makes vim more like stock vi. This keeps things consistent and prevents endless debates. I don't at all mind having a vimrc file with lines commented out that the user can enable. Note that this is the strategy for bash. 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. -- Paul Mackinney | Another look at Sept 11 [EMAIL PROTECTED] | http://www.copvcia.com/
Re: VIM features
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. Feel free to write one :) Wichet. -- _ /[EMAIL PROTECTED] This space intentionally left occupied \ | [EMAIL PROTECTED]http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: VIM features
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 some more of it's better features. Because I'm not willing to for several reasons: 1. every time I enable a feature that makes vim a bit more unlike vi I get multiple bugreports 2. vim is very well documented, if people want to try any of its features they can trivially enable them themselves 3. which features you want enabled is a very personal choice, one that I am not willing to make for users. So I'll always pick the choice that makes vim more like stock vi. This keeps things consistent and prevents endless debates. Also, please keep this thread on debian-user instead of debian-devel, since the choice directly affects the user experience and is not related to Debian development. Wichert. -- _ /[EMAIL PROTECTED] This space intentionally left occupied \ | [EMAIL PROTECTED]http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
