I use Emacs and Vi, using either of these, well, makes you productive. Touting one over the other is never productive. More productive would be for vroom to add a library of FAQ (Flames, Anathemas, Quips), to factor out repetition ;)

I have a one-liner library of perl commands, idiomatic lines..stuff that is too small or generic to justify being in a function or object, respectively.

Being a sick puppy I'll some-day put it into CVS so I could refine the code as I comprehend more. This may make for one liners that are tricky to read, I comment the code.

In defence of my last statement: one place I used to work used a convoluted code generator that produced C code, invariably with 3 levels of redirection, soon everyone could read it, it took exposure to it.

Part of my productivity issue is I try to write terse comments like merlyn's replies to postings.

"It takes me an age to strip out the unnecessary stuff." =~ 
"being concise takes time"
[download]

--

Brother Frankus.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.