vi and perl code highlight

[Luis M]

On 3/3/06, Michael V. De Palatis <mdepalatis at mail.utexas.edu> wrote:
> > I highly recommend using Emacs for editing Perl code.  It has tons more
> > features than 'vim', and is more easily customized and extended.  If you
> > really like he 'vi' style key-bindings, you can use 'M-x viper' or start
> > it with 'emacs -l viper' and say "yes" to the question on start-up.  You
> > won't know until you try it.
>
> Typical emacs user's response :P
>
> Seriously, both vim and emacs are just as good as the other. It's
> really a matter of preference. And before you say this is a typical
> vim user's response, I actually like emacs, too (I know, it's unholy
> to like both).

Agree. This is a typical response from an emac user.

Agree that both are just as good. The only difference (and I don't
want to get into a flamewar here) is:
1. vi is everywhere (installed in all distros by default), so you can
always expect to find it -- or a clone that uses similar/same
keystrokes (heck, even emacs emulates vi with this viper module. i
have never used emacs at all though)
2. vim with all its goodies is about 3 MB to install (the binary
itself is 1.4mb). when i install emacs in dev-servers for my
co-workers, it needs tons and tons of space -- due to dependencies in
pre-compiled binaries.

Aside from that, they are both just as good. Use whichever pleases you
and let others use whatever they want, unless they explicitly ask:
what do you recommend me to use foo or bar? Or something along those
lines.

(that last line goes to Karl of course, not you mike)

Cheers

--
----)(-----
Luis Mondesi
System Administrator
Kiskeyix.org

"We think basically you watch television to turn your brain off, and
you work on your computer when you want to turn your brain on" --
Steve Jobs in an interview for MacWorld Magazine 2004-Feb

No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html