Writing my own text editor, and daily-driving it
Posted by todsacerdoti 4 hours ago
Comments
Comment by bananaboy 20 minutes ago
Comment by whynotmaybe 1 hour ago
Syntax coloring, fast buffering and even a screen saver.
You could even call the compiler directly from it.
All this running on a pentium 120 and it felt a thousands times faster than today's vscode.
But vscode can edit multiple files at the same time...
Comment by willrshansen 2 hours ago
I want to be able to piece together an editor from modular task specific executables. Different programs for file searching, input mapping, buffer modification and display, etc. Probably similar to how LSPs are already separated from most editors.
One step less hardcore than writing a whole editor.
Anyone know of any existing projects along these lines?
Comment by kalterdev 1 hour ago
It steps back from the “customize everything” mantra, believing that approach leaves users with an underdeveloped essential system. But it still has two major APIs: one for window manipulation [2], the other for text-based integration with the surrounding system via plumber [3].
All textual CLI tools (that is, those without pseudographics) work by default and are the heart of its style.
I use Acme for everything except web browsing (although most links are still managed by Acme).
[1]: http://youtu.be/dP1xVpMPn8M
Comment by mudkipdev 1 hour ago
Comment by codazoda 2 hours ago
Comment by altilunium 1 hour ago
Sometimes I get surprise questions from my friends whenever they see my screen. “What’s that?” “That’s my own text editor!”
Comment by willrshansen 2 hours ago
Comment by mllev15 1 hour ago
Comment by abktowa 1 hour ago
Comment by zacklee-aud 2 hours ago
Comment by shablulman 2 hours ago