Oct-18-2016, 03:28 AM
Obviously editing files is important, so why are editors such trash? Emacs is the theoretical best, due to it's incredible configurability, yet it's hindered (imo) by having an interface that's completely insane.
I end up using Visual Studio almost all day, and yet I hate how bloated and slow it is (does intellisense EVER finish loading documentation? ).
If I don't need VS's features, like source control, I'll use notepad++ for quick edits.
So here we are. Files need editing, and I dislike the tools available. What's a programmer to do?
Design the editor they wish they had all along, of course. A few ideas from emacs, the layout of visual studio, the speed of notepad++... hopefully :p
So the plan is to write an event driven text editing engine. Sort of like twisted. Until performance is an issue, I plan on implementing almost all features in user configurable files (including copy/paste). That way, you can change keybindings easily, while having working examples of how to extend the editor. Or, you know, wacky things like having different key bindings for different file types.
So, I have a few ideas on what I'd want this monstrosity to do. But what would your ideal editor look like/do? What ideas do you have for how the interface between text buffers and event handlers should look?
I end up using Visual Studio almost all day, and yet I hate how bloated and slow it is (does intellisense EVER finish loading documentation? ).
If I don't need VS's features, like source control, I'll use notepad++ for quick edits.
So here we are. Files need editing, and I dislike the tools available. What's a programmer to do?
Design the editor they wish they had all along, of course. A few ideas from emacs, the layout of visual studio, the speed of notepad++... hopefully :p
So the plan is to write an event driven text editing engine. Sort of like twisted. Until performance is an issue, I plan on implementing almost all features in user configurable files (including copy/paste). That way, you can change keybindings easily, while having working examples of how to extend the editor. Or, you know, wacky things like having different key bindings for different file types.
So, I have a few ideas on what I'd want this monstrosity to do. But what would your ideal editor look like/do? What ideas do you have for how the interface between text buffers and event handlers should look?