Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!csd4.csd.uwm.edu!leah!rpi!pawl!shadow
From: shadow@pawl.rpi.edu (Deven T. Corzine)
Newsgroups: comp.sys.amiga
Subject: Re: vi versus emacs regexps?
Message-ID: 
Date: 14 Aug 89 20:11:56 GMT
References: <21646@louie.udel.EDU>
Sender: usenet@rpi.edu
Organization: Rensselaer Polytechnic Institute, Troy, NY
Lines: 33
In-reply-to: MROBINSON@wash-vax.bbn.com's message of 14 Aug 89 14:54:14 GMT

[this doesn't belong here!]

On 14 Aug 89 14:54:14 GMT, MROBINSON@wash-vax.bbn.com said:

Robinson> Since I've changed jobs, I've been programming in C and
Robinson> using vi almost exclusively.  The feature of vi that helps
Robinson> me more than anything for C programming is finding the
Robinson> matching (){}'s with by typing % in command mode.  If this
Robinson> was as easy in Emacs, I might still be using Emacs, even
Robinson> though it is slower.  Of course, GNU Emacs has a very good
Robinson> vi emulation mode, in case I would get homesick...:)

I find GNU Emacs to be *much* more useful than vi for editing C code!
It matches open parens for (), {} and [] pairs, and if you type a key
while the cursor has jumped back to show the opening match, it will
jump the cursor back to the point and continue entering data.  Vi, on
the other hand, makes you wait.  [if it's not matching for you, try
M-Esc [Esc-Esc] to evaluate (setq blink-matching-paren t), or put it
in your .emacs...]

Better yet, I have GNU Emacs configured to indent C code in the style
I prefer.  It is very convenient; press tab, and it indents the proper
amount, context-sensitive.  (C-mode understands indententation styles
pretty well.)  [to customize C indentation, study the C-mode docs
carefully.  M-x describe-mode [or C-h m]  M-x c-mode will enter the C
major mode...  if it doesn't automatically when you edit a .c file.]

Deven
--
Deven T. Corzine        Internet:  deven@rpi.edu, shadow@pawl.rpi.edu
Snail:  2214 12th Street, Troy, NY 12180       Phone:  (518) 271-0750
Bitnet:  deven@rpitsmts, userfxb6@rpitsmts     UUCP:  uunet!rpi!deven
Simple things should be simple and complex things should be possible.