My own (call it "c"). At university (1985-9, EE major), there was (MS-/PC-)DOS (CP/M had faded into oblivion). Unix was something heard of but not seen. Ther

My own (call it "c"). At university (1985-9, EE major), there was (MS-/PC-)DOS (CP/M had faded into oblivion). Unix was something heard of but not seen. There was no internet (for starving students). The only sanely priced own-it-yourself computing platform was IBM-PC (clone). I bought a used Sanyo MBC-775. I scrimped to afford the Borland and MS C compilers w/student discount. The Borland IDE was nice, but the MS compiler seemed qualitatively better. And the MSC package had this powerful text editor M. It had almost no UI, but with its "reverse polish" command syntax, box, stream and line selection modes with commands accepting all arg types, I found it tremendously intuitive, Completely customizable key assignments. A macro language. Unlimited undo/redo. It could edit files > 640K (Borland's could not). The manual was well done for those days, and included an API and build process for "editor extensions" (basically DLL's before there were DLL's), which I was soon writing. I was hooked. My brain-finger editor mapping was soon cast for life. Shortly MS replaced M with PWB, which I tried but discarded (bloatware), sticking with M. Years pass, during which I wrote a M clone, now a Win32 console app. Which I use today. While I'm fond of unix (use it for servers at home), all of my employers have been Microsoft-only shops, so my investment in developing my own text editor, which I can change as my needs require, has been worthwhile. Editor vendors in this market have come and gone (Brief, Codewright to name a few of the more popular), and their users have been disrupted. I just "keep on truckin" with my own... If the need arises, maybe I'll port to Linux/BSD.