Re: Any good Perl Editors for Linux?

You should check out the Perl Development Tools Editor/IDE comparison chart to find the answers you seek.

With that said, I'm amazed that vi/vim and emacs are being so highly recommended. Both are complex and hard to learn. Given that you are currently going to be a "casual" Linux user neither seem appropriate. [ Though learning some basic vi/vim might be a good idea if you expect more exposre to UNIX/Linux/BSD environments as it is usually the only editor you can safely assume will be there. ]

Some editors that would (imo) be more suitable are the underrated NEdit, the very popular EPIC (which also runs on Windows), and for KDE desktop users the popular KDevelop. Based on your post I would suggest you give NEdit a try first (good feature set and it should be easy to install).

Comment on Re: Any good Perl Editors for Linux?

Replies are listed 'Best First'.
Re^2: Any good Perl Editors for Linux? by cls (Initiate) on May 07, 2006 at 19:16 UTC
Learning vi is a worthwhile investment for any developer. It's the editor you can assume will be just about anywhere, (You might have to bring it with you.) Learn vi before vim, so you don't become dependent on vim-specific enhancements. Start here. http://docs.freebsd.org/44doc/usd/12.vi/paper.html Ignore the obsolete stuff about teletypes, broken character terminals, and slow modems, and it's pretty short. And it starts you on the right track: visual edit commands are all <operator><count><cursor-motion>, not a whole bunch of arbitrary things to memorize. If you go at it that way, and they tell you where ex(1) ends and vi(1) begins, vim actually makes some sense. Among the vim\|elvis enhancements, "left click" became just another cursor motion (unfortunately it doesn't like <count>) and "center click" a synonym for paste, but the language underneath stayed the same.	[reply]

Replies are listed 'Best First'.

Re^2: Any good Perl Editors for Linux?
by cls (Initiate) on May 07, 2006 at 19:16 UTC

Start here.
http://docs.freebsd.org/44doc/usd/12.vi/paper.html
Ignore the obsolete stuff about teletypes, broken character terminals, and slow modems, and it's pretty short. And it starts you on the right track: visual edit commands are all <operator><count><cursor-motion>, not a whole bunch of arbitrary things to memorize. If you go at it that way, and they tell you where ex(1) ends and vi(1) begins, vim actually makes some sense.

Among the vim|elvis enhancements, "left click" became just another cursor motion (unfortunately it doesn't like <count>) and "center click" a synonym for paste, but the language underneath stayed the same.

[reply]