vi or emacs for editing Python on Linux?

IBMackey ibmackey at hotmail.com
Sun Dec 23 10:59:56 EST 2001


Bas van Gils <bas.vangils at home.nl> writes:

> On Sun, Dec 23, 2001 at 08:19:56PM +0900, Jonathan Gardner wrote:
> > Bottom line: You have to spend at least a week using both editors before you 
> > can make a good decision.
> 
> I agree with Jonathan. I started of on linux/unix using pico, and moved
> on towards vim, mainly because my co-workers used it. After a while I
> tried using Emacs and found it a nice editor as well, after struggling
> with the key-strokes :-)
> 
I dabble a bit with python. But I spend a whole lot of time with
editors. The closest I've found for ms users is nedit. The nedit
manual is perhaps 50 pages long, but nedit does everything
Emacs/Xemacs does. It's logical. Macros, recordable and programmable
are easily mastered. I took a half day after reading the manual to
setup an auctex-latex environment, lisp debugger and program cycle,
python, python-docs, debug cycle. Nedit is also available for ms.

BUT, and this is why I use xemacs, it doesn't have gnus. Not a problem
for most ms people, but gnus is phenomenal. It automatically downloads
mail and news, sorts it, plus scores with artificial intelligence your
most read authors and subjects. It can kill with precision. If it
wasn't for gnus, I would still use nedit...

ib



More information about the Python-list mailing list