Date: Sat, 23 Sep 2000 19:57:22 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: Francesco Casadei <fcasadei@inwind.it> Cc: questions@freebsd.org Subject: Re: perl/cgi Authorintg tools Message-ID: <14797.20850.815606.526798@guru.mired.org> In-Reply-To: <37728805@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Francesco Casadei writes: > On Fri, Sep 22, 2000 at 09:22:46PM -0700, Doug Barton wrote: > > I don't want to start a holy war here, and in fact, I wouldn't mind to > > find a fancy editor myself. I've stuck with vi because it's available on > > all the platforms we use at work. > I didn't know vi had all that wonderful features. I must confess that > I adopted a 'first-fit' policy to search for a good editor. Evidently > I discovered Emacs before Vi! :-) So did I, and not on Unix. However, anyone who regularly works on Unix - any variety - would be doing themselves a favor to learn vi. I tend to do all my work as me in emacs (I'd use it for browser if I had a separate thread). However, I don't like the idea of having root running that large an environment - especially when it's not obvious which emacs window belongs to root, and which to me. So I tend to use vi as root. Unless it's something simple, in which case I use either ed or ex (depending on what my fingers do), because there was a time when vi wasn't everywhere. I don't know if anyone ever did a perl interpreter mode for emacs, but other interpreted languages include the ability to run an interactive interpreter in a window, so you can load and test modules, cut-n-paste code without touching the mouse, and other good things. It manages to provide many of the features one finds in language-specific IDE's. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14797.20850.815606.526798>