I used to use an IUO editor that had a very powerful, c-like macro language built-in. I wrote some amazing macros using it; like one called picoDraw that allowed you to drag the cursor with the arrow keys and draw perfectly formed boxes and tables using the old OEM line-draw characters. As trails crossed, the appropriate corner, tee or cross piece was left behind.

I now, and for a long time, use a relatively simple programmer's editor with nothing more than a keystroke recorder/replay macro facility; a built-in file-compare, and a customisable, call external tool facility and little else.

The problem with the all-singing, all-dancing, totally customisable editors is that: a) they are never particularly well configured from the get go -- better to "start minimal and allow the users to do there own thing" they reason; b) you are never quite satisfied with them. There is always another mode, plug-in or macro that helps in some obscure, occasional situation that can be added.

And the problems with that are: a) you're forever customising it; b) forever debugging the latest additions and the interactions between them; c) forever downloading the latest versions of those in order to stay current; d) never quite commit the multitude of different modes and key sequences to mind and muscle memory. So you never quite become fully familiar with your tool.

Whereas my simple editor since circa. 1995. It has gone through 4 or 5 major and myriad minor updates in that time; and yet almost nothing has changed. I mean nothing that impacts my nearly 20 years of muscle memory. Its got prettier. Gained a few things. But for the most part I can switch between versions and unless I go looking, not actually notice any change. (It even has the same few minor annoyances!)

When it comes to the most important tool in the programmer's kit, there is an awful lot to be said for stability.

Any manipulations the keystroke macro facility can't handle tend to be one-offs; so I use a perl one-liner to do them. If I find myself doing the same thing a second time, I make the one-liner a script and tuck it away in a dusty corner of my disk in case I need it again. The only real problem then is trying to name them to something one will recognise a few years down the road.