OK so I am guessing an editor war would not be welcome here ;-) I would recomend looking at vim tho if you were new to the editing world. It has a very very snazzy perl interpretor built into it, it allows you to run perl over the current buffer (amongst other things). I am an emacs head really, but the idea of running perl in an editor has long been one I think has wings. Shame I am too stuck into lisp atm ;-(
--
Zigster | [reply] |
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"
--
Brother Frankus. | [reply]
[d/l] |
