Re: Vim to Vi (Was: weird defaults in Feisty)
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 probably need > to run update-alternatives to ensure that /usr/bin/vim points at the one > you want. > > -- It doesn't really matter if it is replaced or both be installed. What I care is: when I installed a fresh version of Ubuntu Feisty, type vi, I got the Tiny version. After I apt-get installed the vim-gtk, then I type vi, I got the Big version. So, you see, vi is "replaced" from Tiny version to Big version, that's what I had observed. -- Sincerely, Pan, Shi Zhu. ext: 2606
Re: Vim to Vi (Was: weird defaults in Feisty)
[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 of vim, and the vim will be replaced with that version. Well... not replaced. They will both be installed. You'll probably need to run update-alternatives to ensure that /usr/bin/vim points at the one you want. -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ signature.asc Description: OpenPGP digital signature
Re: Vim to Vi (Was: weird defaults in Feisty)
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 said, we upgraded and he was just > like, "vi got totally weird and now I use nano!" But after having > explained to him a couple things that might help him out (r for > replacing single characters and whatnot) I think he might start the > path to enlightenment ;-) > > -fREW 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 of vim, and the vim will be replaced with that version. I don't see any problem now, in Feisty, I just run "vi" and everything is okay, I do *never* use command "vim" to run vim, runing vim with the command "vi" feels much better for me. Anyway, I don't think any experienced vim users will still think he need a plain "vi" after he had get used to "vim". So it is wield for me to have two different versions of vim on my single computer. -- Sincerely, Pan, Shi Zhu. ext: 2606
Re: Vim to Vi (Was: weird defaults in Feisty)
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
learning of GNU/Linux, by the way) was as follows:
1. Use it as a Notepad with weird save/quit commands (:w ...)
Always in insert mode, only using the arrows, Del, BS, Home, End, and
hitting Esc and 'u' like crazy whenever something weird happened.
2. Learn "copy & paste", first line-wise (dd yy p P), then selection-wise
(v V ^V y d, still only using the arrow keys.
At this point (a few months?) I was already as productive as with my
former Windows editor of choice! (something like TextEdit™ or TextPad™)
3. Learn that command mode is actually useful for moving around in the
file (gg, G, {, }) and opening two files at a time (:e, C-^)
4. Other stuff (complex movements, buffers/windows/tabs, registers,
macros, mappings, autocommands, folding, custom syntax files...)
This timeline might look non-linear, in fact I believe that learning Vim
is an exponential task to the engaged user, and that's a very good thing!
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
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 said, we upgraded and he was just
like, "vi got totally weird and now I use nano!" But after having
explained to him a couple things that might help him out (r for
replacing single characters and whatnot) I think he might start the
path to enlightenment ;-)
-fREW
Re: Vim to Vi (Was: weird defaults in Feisty)
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 that your path is non-linear, I've actually learned vi after vim, which is even more backwards haha. Some servers I need to admin have nano and vi... I'd much rather use vi than nano, even though nano is "easier" to most people, because to me vi is "like" vim. Of course vim is the clone, not vi, but since I learned vim first that's what I've grown to expect. --Mike H
Vim to Vi (Was: weird defaults in Feisty)
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:
1. Use it as a Notepad with weird save/quit commands (:w ...)
Always in insert mode, only using the arrows, Del, BS, Home, End, and
hitting Esc and 'u' like crazy whenever something weird happened.
2. Learn "copy & paste", first line-wise (dd yy p P), then selection-wise
(v V ^V y d, still only using the arrow keys.
At this point (a few months?) I was already as productive as with my
former Windows editor of choice! (something like TextEdit™ or TextPad™)
3. Learn that command mode is actually useful for moving around in the
file (gg, G, {, }) and opening two files at a time (:e, C-^)
4. Other stuff (complex movements, buffers/windows/tabs, registers,
macros, mappings, autocommands, folding, custom syntax files...)
This timeline might look non-linear, in fact I believe that learning Vim
is an exponential task to the engaged user, and that's a very good thing!
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
