Emacs can do all of this, though real thorough code completion is really dependent on the support of and mode for the language you're using. There are a whole bunch of generic completion minor modes too, so you'll never be completely without it if you don't want to.

For perl, I don't really use the debugger much at all. You may also be interested in Sepia, which runs an "inferor perl" more or less like Slime for Lisp, which means it can catch/debug exceptions when they occor, do completions based on whatever is currently defined in your running perl process etc. This is a pretty different way of developing than the usual save/compile/run methods, and suits some kinds of programs better than others.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.