Writing my own text editor, and daily-driving it
blog.jsbarretto.com
Writing my own text editor, and daily-driving it
1–10 of 124 posts
Re: Writing my own text editor, and daily-driving it
#2[flagged]
Re: Writing my own text editor, and daily-driving it
#3I use my own text editor too. Nobody else seems to get value from it. I’m still surprised by the value we get from home grown solutions.
Re: Writing my own text editor, and daily-driving it
#4[dead]
Re: Writing my own text editor, and daily-driving it
#5I use my own text editor too. Nobody else seems to get value from it. I’m still surprised by the value we get from home grown solutions.
Didn't even link it. :(
Re: Writing my own text editor, and daily-driving it
#6This feels like two steps up from a highly customized vim config. But I want one step up.
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?
Re: Writing my own text editor, and daily-driving it
#7This feels like two steps up from a highly customized vim config. But I want one step up. 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 pr…
Acme [1]
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
Re: Writing my own text editor, and daily-driving it
#8Should make my own text editor. Would make for an interesting project at least.
Re: Writing my own text editor, and daily-driving it
#9I use my own text editor too. Nobody else seems to get value from it. I’m still surprised by the value we get from home grown solutions.
I use my own text editor too.
Sometimes I get surprise questions from my friends whenever they see my screen. “What’s that?” “That’s my own text editor!”
Re: Writing my own text editor, and daily-driving it
#10I would recommend using the ropey crate for easy performance gains. A string buffer is quick to implement but you will hit a wall as soon as you need to edit large files.