Re: Vim to Vi (Was: weird defaults in Feisty)

2007-05-23 Thread panshizhu
Micah Cowan <[EMAIL PROTECTED]> 写于 2007-05-23 09:11:54: > [EMAIL PROTECTED] wrote: > > All you need to do is to: sudo apt-get install vim-gtk, which installs a > > Big version of vim, and the vim will be replaced with that version. > > Well... not replaced. They will both be installed. You'll proba

Re: Vim to Vi (Was: weird defaults in Feisty)

2007-05-22 Thread Micah Cowan
[EMAIL PROTECTED] wrote: > It seems nature to have vim behave like vi, if the Linux distribution > choose to do so. The distribution decides everything and it is non-related > to vim developers themselves. > > All you need to do is to: sudo apt-get install vim-gtk, which installs a > Big version

Re: Vim to Vi (Was: weird defaults in Feisty)

2007-05-22 Thread panshizhu
fREW <[EMAIL PROTECTED]> 写于 2007-05-23 08:15:55: > Yeah, the really big problem is that the guy I am working with who I > am helping admin a few servers is at exactly step 1. In fact, it > wasn't until recently that he figured out (I told him) that Ctrl-Z is > not the same as :q!. And like you sa

Re: Vim to Vi (Was: weird defaults in Feisty)

2007-05-22 Thread fREW
On 5/22/07, Tobia <[EMAIL PROTECTED]> wrote: David Nečas (Yeti) wrote: > it's a bit strange when a vim user describes vi as `crazy' and `so > weird'... It may sound strange to us Vim veterans, but it's what I would expect. My path to learning Vi/Vim (which took place at the same time as my lear

Re: Vim to Vi (Was: weird defaults in Feisty)

2007-05-22 Thread Michael Hernandez
On May 22, 2007, at 3:11 PM, Tobia wrote: The point is: I don't consider my learning path in any way peculiar, and if Vim had suddenly reverted to Vi while I was in phases 1 to 3, I would have looked at my computer with a blank, baffled expression on my face. Tobia If you find th

Vim to Vi (Was: weird defaults in Feisty)

2007-05-22 Thread Tobia
David Nečas (Yeti) wrote: > it's a bit strange when a vim user describes vi as `crazy' and `so > weird'... It may sound strange to us Vim veterans, but it's what I would expect. My path to learning Vi/Vim (which took place at the same time as my learning of GNU/Linux, by the way) was as follows: