Could you tell me what you use a text editor for if not for programming? If that's true, then i'm in the same situation as yourself. But I don't know what features to look for in a text editor. And i feel like everyone else that talks about text editors focuses on the programming, so i never can relate.
I touched on that at the top of my article. I typed that very post in EmEditor (via this Firefox add-on). But the heavy-duty stuff I do is related to my work in translating software and websites. Often I review translations in xml and other formats, where the tags are dense and must not be damaged. Other times I make global changes in files, or extract text from in-between the tags, e.g. to do a proper spellcheck without the spellchecker stumbling on the tags and various codes. I clean up translation memories to generate glossaries for my own use, which involves stripping not only xml tags, but random RTF codes and similar crud. And I as I mentioned in the post, these files are often pretty big, and they are almost always Unicode.
So in my case it's not so much creating new files (whether prose or program code) - it's more of reading, navigating, searching for and replacing stuff, doing all sorts of tweaks and transformations. That's also why I need capable macros, or better, editable scripts to automate tasks and adapt to changes.
I should say that most people in my line of work probably don't do all the stuff I do. There are specialized tools for localization, which I also use, but they are awfully limited in their editing capabilities (and forget about macros). There are things that I can do much faster in a text editor, and there are things which I would be entirely unable to do without one. For example, I sometimes need to edit parts of files which the professional translation tools (hundreds of Euros per license) won't even let me touch. I also use a dictionary program I wrote (called Tranglos - my domain was set up to publish it), and for that I need to convert from or clean up various bilingual files. I've written a converter, but often I use regular expressions in a text editor to prepare files, even if it's just to change the structure of a file because it's faster than recompiling my converter
Speed of keyboard operation also counts, since I sell my time. Any function that's not keyboardable means I take longer to finish a task. That's one reason I love EmEditor's way of assigning more than one key combination to a function: that way I can have four (4) different ways to invoke Find (I use three of them commonly, without thinking of which to use or why). It's also why EditPad Pro's search, though powerful and visually pleasing, throws me off a little, since it's designed more to be used with the mouse.
I try to use the most convenient tool for a job. I won't fire up Oxygen to edit a word in an xml file - EmEditor is fine for that; but Oxygen is very helpful when I need to figure out the structure of a large xml file, or validate one, make global changes or extract whole blocks of xml.
I hope my post doesn't come across as a bunch of complaints. It's fun to juggle all those editors and discover what they can do - and the Grid view in Oxygen (pictured in one of the screenshots) is truly a sci-fi kind of beauty.
