Emacs is the way to go (he says, donning his flame-retardant suite). I use
it on both window$ and Linux.
It does color-coding and auto-indenting. It has a menu so you don't have
to learn all those Ctrl and Esc keystrokes, but if you learn the ones you
need (I get by with about 10), you'll be at home in a telnet session.
Don't be afraid.
Let the holy war begin.
At 02:02 PM 1/10/01 -0500, Matthew Brooks wrote:
>I'm interested in hearing what people use as their code editors in their
>respective environments and what their opinions are of them.
>
>When I'm stuck on the MS platform I use CodeWhiz, which is a neat little
>program that formats key words and functions while I type.
>Unfortunately, I haven't figured out a way of getting it to recognize
>$foo, %foo or @foo as something to format so I'll only give it ***1/2
>out of 5 stars.
>
>Under the *nices I generally use pico (and vi when pico is not around),
>in part because I haven't found a code editor that does anything special
>with perl code and also because I'm sometimes connected remotely to the
>machine. Maybe it's time to learn emacs, but my head hurts every time
>I've tried it.
>
>
>Matthew
>
>#.sig here
>use perl || die "Et tu Brute?!: $!\n";
---------------------------------------------------------------------
Joel Gwynn Designers' CADD Company, Inc.
A bus station is where a bus stops.
A train station is where a train stops.
So now you know why they call this a workstation...
