On Tue, 2009-04-21 at 22:08 -0400, patricia campbell wrote: > It has a high learning curve & if you are easily frustrated it you > might not make it over but it is worth it if you force yourself to use > it exclusively for a while. It is a fantastic tool for all of the > reasons stated below. I object to the "if you are a coder it's a > different matter" though I worked with a great team that used vim > variations exclusively on a 2 year telecomm project in 1999-2001 w > sockets & x.25 communications on HPUX, AIX & some proprietary > hardware. We wrote & tested many twisty windy lines of code (a count > which I think is no measure of quality or value btw) & a great product > once we'd finished. > > That said, you need VI because one day you will be stuck & it will be > the only editor available... (btdt) > > Tricia > > On Tue, Apr 21, 2009 at 7:42 PM, Peter Silva <[email protected]> wrote: > > > > There is no other editor around that let´s you keep your hands on the > > qwerty part of the keyboard. Cursors, pgup/down, home, end, are all > > useless fluff. > > That means you can type much faster, with much less hand motion. > > > > The integration of regular expressions via : commands, make search > > and replace as powerful as awk, far easier than other editors. Uses > > less memory than other editors, by far. > > > > :wq > > > >
I do use vi/vim when editing config files, it works quite well for that with the limited vim knowledge I have. It's when it comes to writing code that I find it slows me down. Perhaps you could share how you use vim? Do you use multiple tabs/windows? I tried the vim tabs and they just don't work as well as gedit/kate tabs (specifically switching between them). thanks, nick _______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
