Honestly I really want to make one. Mostly because I want to stay in my terminal as much as possible, but I'm super fast with VSCode's keybindings and I can't handle the velocity drop during the learning curve.<p>Alternatively, if it's possible to emulate VSCode's keybindings in an existing editor, I'd be happy to go that route. I just don't know the space very well.
why?? TECO (now TECOC Type Every Character Over Constantly) is perfection as a cli editor<p><a href="https://github.com/blakemcbride/TECOC">https://github.com/blakemcbride/TECOC</a><p>seriously. try it.
> const tabSpaces = 2;<p>Shots fired.<p>Building your own editor is a fun project for sure. Curious with node whether you can build it into a single executable that you can, for example, conveniently scp around to host:.local/bin/
Made my own CLI text editor as well this year using rust following this:
<a href="https://www.flenker.blog/hecto/" rel="nofollow noreferrer">https://www.flenker.blog/hecto/</a><p>Building tools like this is great practice for learning new languages.
It's pretty easy to say "terminal based" or "text mode" instead of CLI, which is misleading. I was expecting an alternative to sed.
Yes! We need more "because I can" and "because I wanted to" in this. More art, less ... idk what to say here ... less formality. Some of the most fun projects I've done were ones that I knew already existed but I just had to -know- what it'd be like to write one.<p>Good work Tom :) I'll give it a shot BECAUSE I CAN!
> Maybe should be THE (Tom's Hubristic Editor).<p>A TUI editor called THE already exists: The Hessling Editor, a work-alike of xedit.<p>1. <a href="https://hessling-editor.sourceforge.net/" rel="nofollow noreferrer">https://hessling-editor.sourceforge.net/</a>