4 ms·
Way to be subtle with that last paragraph. :P I'd actually approach the issue from the other end (that is, frontend) - There is a slight pain point in the stro
by jrajav 14y ago
Way to be subtle with that last paragraph. :P
I'd actually approach the issue from the other end (that is, frontend) - There is a slight pain point in the strong binding between vim and terminals in that, as this video points out, the UI is limited by a character grid. This makes many features uglier and less usable, such as autocomplete, file viewers, the command line, the gutter, etc. It also limits your choices for fonts.
If I were to design a "modern" vim from the ground up, I'd probably arrive at something a lot like Sublime Text 2 with vim at the core.
- jlgreco 14y agoOh, don't get me wrong, I am a Vim user who can't stand Emacs. I just think that Emacs was engineered better. ;) I think that re-engineering Vim to be more like Emacs under the surface would lend itself well to other things, like what you are suggesting.
- Peaker 14y agoViper?
- jlgreco 14y agoI gave it a shot, but I didn't like elisp enough to stick with it.
- snogglethorpe 14y agoNot really better engineering[+], I think, so much as perseverance—Emacs originally had the same character-grid limitation, and has gone through multiple display-engine (etc) rewrites to get to the point it's at now, and the amount of pain involved along the way has been ... considerable. There are still limitations stemming from the original design that are going to require even more pain to remove. [+] This isn't a diss, mind you—I use Emacs, and love it, and have done a fair bit of Emacs development.