I started writing a text editor.

I started writing a text editor on May 18, 2025.

Initially it was my first experiment in “Vibe Coding,” but after achieving a positive looking prototype, I started to encounter limitations and decided to get more serious about it.

Here's a rough screenshot of the initial attempt, taken on May 19:


By the next day, I had cleaned up a lot of the look and feel to be closer to my vision:


However, on that same day, May 20, Microsoft announced a new version of Edit.  The successor to their EDIT.COM from MS-DOS, which had originally been released in 1991 and whose last stable release was version 2.0.026 in 1995.  (See https://en.wikipedia.org/wiki/MS-DOS_Editor and https://www.ghacks.net/2025/05/20/microsoft-releases-edit-an-open-source-command-line-text-editor-for-windows/.  I was absolutely shocked, but I also knew EDIT — or its new incarnation, while nostalgic, was nowhere near what I had in mind, so I considered this a bit of a challenge, and I continued working on my goal:

My initial project was in TypeScript, which I had been learning at the time.  The fact that it was single threaded and forced to use the awkward async/await system which colored functions and any function which called those functions was problematic for my vision.

I also knew I needed a rock solid data structure under the hood for what I was trying to achieve.

Goals:

  • Possibility of WordStar-style Keybindings
  • Editing Massive Files without Slowdown
  • Must be able to run in a Terminal, over SSH
Early on, I realized my keybindings should map to relatively generic callable commands or macros, and I thought it would be fun if the things they are bound to are actually snippets of dispatch code.  I knew these would need to look like “blocking” functions to the caller, because I didn't want to subject my users to writing async/await style hell to accomplish simple tasks.

From this frustration was born a completely different project:  PawScript.


I decided to use Go (golang) to write PawScript since I wanted to leverage their concept of goroutines to achieve a real multithreaded system.

To make a long story short, PawScript led me to a different sidetrack, because I wanted to make a GUI interface to make it easier to experiment with, but I wanted the feel of writing a console app to still exist, so I made a spiritual successor to my old PerfecTerm from 1996.  Wait... what was PerfecTerm?

Well, in the mid ’90s I was running a dial-up Bulletin Board System, and I wanted to make my own BBS “server” software (we didn’t call them servers back then, though.)






I was also writing several BBS door games at the same time, including Kitty Litter, which became mildly popular (it was like a blend between Solar Realms Elite and Barney Splat—if you were there, you were there) ...




As part of the BBS hobby, I also wrote my own Terminal Emulator, called PerfecTerm.  It was a bundle-in included with the PREDATOR BBS system.



I never really released PREDATOR to the public, but, in 1997 I volunteered at the PRA (Pacific Racing Association) races held at Douglas County Speedway in Roseburg, Oregon, where I learned enough to, along with another programmer develop a system we called TRACKMASTER— a computerized race scorekeeping tool.  (No relation to any company called that in modern times.)   And, we eventually were asked if we could also handle ticket sales for the general public attending the race, so we started to develop another product, which ran on a RedHat Unix 5.0 Hurricane box tucked away in the pit office, via serial communication links through a bundle of Cat6 cable that was run along the fence and through a pipe which we buried in a trench we dug ourselves underneath the pit area gravel lot.  We wrote the first version of TrackMaster in about 3 days in Turbo Pascal, ported it to a Free Pascal compiler on UNIX, and then we wrote the ticket system in a similar way.  We had run out of Wyse and DEC dumb terminals, however, and we needed a way to interface with receipt printers.  So, I added a code to PerfecTerm to allow us to switch between outputting on the screen and printing to a printer connected to the same computer.  We had a bunch of leftover, decommissioned IBM PS/2 machines with no hard drives, only floppy, and I was able to get PerfecTerm to boot off the floppy, turning those machines into useful point of sale ticket sales terminals.  We wanted to call it TicketMaster but were sad to discover that name was already taken, so our Ticket system was never given a name of it own, and just remained part of TrackMaster, but this was the first use of PerfecTerm for anything non-hobby, and it was great to see.

I was still only 16 years old at that time.

Fast forward 28 years...


I used AI and my extensive knowledge of ANSI and VT100-style emulators to put together a modern re-envisioning of PerfecTerm to use as the display engine for my GUI for PawScript, so I called it PurfecTerm.  (Soon, I was thinking, I could port the old Kitty Litter door game to it and have a version that could run natively on modern computers...)


I may have gotten a little carried away with CJK double-wide characters, RTL Hebrew and Arabic support, and ridiculous visual effects.  I added a tile-based background, smooth scrolling, and sprite overlay system to it, bringing its retro vibes approximately into the same realm as the PPU on the Nintendo Entertainment System.

Next, I turned to the task of exposing the GTK or Qt widgets natively to the PawScript coder.  I wanted them to be able to create a window with labels, buttons, checkboxes, and all the other widgets with relative ease and simplicity.  I wanted it to feel like the 1990s, but work like a modern GUI app.

But around this time, I got very frustrated with GTK and Qt.  They were hard to work with.  And, I also felt annoyed that any program I wrote in this way would be locked in to one platform, and no longer run in the Terminal.

So, I made my own TUI system, and to make things more ridiculous, I turned PurfecTerm into a widget in that system as well, albeit with slightly less capability than the GTK or Qt versions.


I added mouse support for terminals that have mouse event reporting, but I focused on complete and easy keyboard accessibility, and have even put substantial effort into making it support voice announcements for those who need to rely on screen readers.

This was really good.  But, I knew my friends on other operating systems, or just those without much console experience would not be able to appreciate this quite as much...  so I decided to port KittyTK to SDL and make a graphical version of it, meanwhile separating out the application interface to be a protocol based display server so that the application doesn't have to have any of the graphical dependencies compiled in, nor even know if it is going to be displayed on a text or graphics screen.


This project, while cool, seems quite far from my original intent to write a text editor, but that was about to change.

I started to do an audit of what features I might still be missing to be truly competitive with GTK or Qt, and I asked Claude Fable (which had just come back online after being taken down by order of the US Government) to take a look at it.

Claude reported back that I was missing two major components.  A columnar grid view.  Yeah, ok...


Backported to text:


And the other missing component:  A multi-line text editor.

Hey wait...  Funny thing, that....

A couple days hardening PawScript and Garland (did I mention Garland? ... a Rope-based storage engine with decorations (named marks that slide along with the data to track with inserts and deletes), and full undo/redo and branching history.)

July 18, 2026:


That's not just the console version of mew running in a PurfecTerm, that's an “editor” trinket in the same process as the KittyKT display server being rendered as an inline trinket borrowing only the PurfecTerm display surface code.


Yesterday, July 19, 2026, I reached enough feature parity with my daily driver text editor that I was able to use mew as my main code editor for the entire day, for the first time.

By the way, my daily driver text editors over time have been:

  • TED by Tom Kihlken (1988, PC Magazine) which I used in DOS 3.3, 5.0, 6.2...
  • The Turbo Pascal 7 IDE, which was my first formal introduction to WordStar-style shortcuts.
  • pico (Pine Composer, 1989, University of Washington) which I begrudgingly adapted to in order to code on UNIX, and...
  • nano (Chris Allegretta, 1999, the GNU clone of pico, now maintained by Benno Schulenberg)
  • The Borland Delphi 7 IDE, which ported most of the keyboard shortcuts from TP7 to Windows.
  • JOE (Joe’s Own Editor, Joseph H. Allen, 1991, maintained by Marek ‘Marx’ Grac and others since 2001, with Joseph Allen returning to the project in 2004.)
And, finally, at long last:
  • mew (mew edits words, 2026, Jeffrey R. Day—that's me!)
For those wondering, I have tried vi, vim, and emacs.  They are both beautiful systems, but I have rather enjoyed occupying a middle ground with JOE, and I think mew will carry on well in that middle space while adding more of the types of things that emacs has been known for.

Late last night, I started to add scaffolding to build a help system.  I'll save that for the next post.  Once I have a rudimentary help system in place, I will make the first public release.

It has been quite a journey.

Comments

Popular posts from this blog

History of mew, 2025