The Editor Is Done Enough. Time to Write.

Last month I set out to write a book. What I actually did was build a LaTeX editor.

The plan was always “just fix this one thing, then get back to the manuscript.” One thing became a build pipeline, then SyncTeX, then an AI panel, then a minimap, then session restore, then — you get the idea. The git log reads like a confession.

But somewhere in the last week or two, something changed. I’d sit down to write, reach for a feature that wasn’t there, and find that… it was there. Forward search landed exactly where I expected. The outline followed my \include chain without complaint. The build target stayed pinned to main.tex no matter which chapter I wandered into.

The editor stopped getting in my way — which was the whole point, one detour and one month ago.

So this week, I opened chapter3.tex. Not to test bracket matching. To write.

texspark isn’t finished — no software ever is. There’s still a list of things I want to build, and the changelog will keep moving. But it’s crossed the threshold from “project I’m building” to “tool I’m using.” The dogfooding phase is over; the dog is fed and the food is fine.

The book is about machine learning, written in Korean, typeset in LaTeX — obviously. If the editor holds up through a few hundred pages of equations, figures, and my questionable prose, you’ll know the 1.0 badge was earned.

Back to the manuscript. For real this time.