https://news.ycombinator.com/item?id=15386994
Emacs comes fairly close, but not close enough for me.
What I want is modularity to the extreme. I want to define an entire UI/UX as a user without running into roadblocks.
I have envisioned a set of default UIs that the user can simply override, or reference in their own UI. This way a new user is presented with a familiar editor, but can cleanly step away from defaults. No workarounds.
> I'd be rather interested in what you end up with.
My problem is that I care so much about planning ahead that I have started over several times. It would be very helpful for me to get feedback from others, and bounce ideas back and forth.
I am considering putting a serious effort into this project, since I am currently unemployed, and need to build a resume, etc.
It looks like there are quite a few of us. I wonder how many would be interested in putting a group project together. I would really like to consider and hash out some ideas with a group.
I love emacs, use it daily, and think that it's positives far outweigh it's negatives, but hooo boy sometimes you need to wade through decades of muck to make it do a thing, and it's often not clear what the best way to go about trying to do a thing is, particularly to people who haven't been using emacs for a decade+.
Evil-mode is nice in this regard, but I don't want Vim's defaults either, not to mention Emacs' bindings are still there, just hiding in insert mode.
The feature I want the most (that isn't readily available in an editor) is to define keybindings from scratch. I don't want to deal with undoing everyone else's work just to get started on my own.
And programmers spend most of their day interacting with a text editor, so many hold strong opinions about them (see editor wars).
It is likely that some will not find one that fit their needs, and thus build their own.