On Sun, Aug 10, 2008 at 6:43 PM, William L. Maltby CentOS4Bill@triad.rr.com wrote:
On Sun, 2008-08-10 at 15:40 -0700, Akemi Yagi wrote:
On Sun, Aug 10, 2008 at 3:11 PM, Frank Cox theatre@sasktel.net wrote:
On Sun, 10 Aug 2008 17:04:16 -0500 Lanny Marcus lmmailinglists@gmail.com wrote:
Should I try to learn vi (Vim) (which obviously will help me, if I ever need to administer a remote box) or install Emacs or something else, for the gcc editor?
These two usually result in religious wars. Emacs is *very* powerful and customizable and extensible. Probably makes the learning curve longer. But it already has definitions for several languages. Vim also has some.
Bill: I am going to have a *huge* learning curve with C++, so I am going to go with vi (vim) or something *very* close to it and avoid the long learning curve of Emacs. Emacs is a completely different breed. Apples to Oranges.
I never used emacs much as I already had a "cake walk" into vi (now vim) because it uses a lot of what you find in regex, which I was intimately familiar with, from heavy "ed" usage before vim was a gleam in someone's eye.
I used an Intel editor, years ago, that probably was something like vim. Prefer not to need to memorize, but if I use it often enough, I will learn it and be able to use it.
If you already have some familiarity with regex (grep, sed, et al), you'll probably find vim faster to learn.
No experience with those.
Then I would suggest that. Otherwise, take a quick browse of the man pages for both, pick one or the other and use it (almost) exclusively. You'll quickly become competent if you use it a lot and take brief reads of succeeding sections in the man pages or tutorials.
Vi or vim. I think Emacs would just cloud my mind, when I'm trying to absorb C++ Lanny