4 ms·
I am wondering in what way a "modern vim" isn't "vim". GVim exists, and plugin management is a problem frankly solved years ago. I also wonder how he is going
by jlgreco 14y ago
I am wondering in what way a "modern vim" isn't "vim". GVim exists, and plugin management is a problem frankly solved years ago.
I also wonder how he is going to support modern features that Vim currently has with a web-based editor. Can I script this in my choice of modern languages? Python? Ruby?
If I were going to change any single thing about Vim, it would be to make MzScheme scripting support a first class citizen, and slowly re-engineer the backend to be more Emacs styled. Core C (or whatever, but C out of momentum) functions with the rest of the system build up in Scheme. I think it would be foolish to call such an improvement "modernizing" though, since it is hardly a new idea. ;)
- ecspike 14y agoChrome Packaged Apps are essentially a Chrome extension with some extra features that can run outside a browser instance. As such, scripting would be limited to languages that can run in JS. So if he allows plugins, it would be JS, CoffeeScript, or possibly Emscripten.
- jlgreco 14y agoThat is what I suspected. Kind of makes the idea of using that sort of system to create generic modern developer tools DOA I think. Definitely so if it means I lose Vim's ! command; I couldn't live without that.
- ecspike 14y agoI agree. You can make unitaskers like sprite packer/unpackers image quick editors/resizers and the like but anything comprehensive is going to be hard.
- jrajav 14y agoWay 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.
- guns 14y ago> If I were going to change any single thing about Vim, it would be to make MzScheme scripting support a first class citizen, and slowly re-engineer the backend to be more Emacs styled. Core C (or whatever, but C out of momentum) functions with the rest of the system build up in Scheme. Thank god there are people who share this vision! I have solemnly promised to myself that I will write a new vim in exactly this fashion if no one has done so in the next 10 years. One thing that I don't understand about contemporary developers is the aversion to running their editors in a terminal. The benefits of doing this are significant (e.g. session management with tmux, remote pair programming via the same), but programmers leave them behind for what is ultimately just eye candy. The major reasons for this are the difficulty in binding complex key chords in a terminal, and the poor implementation of OS X's Terminal.app (both of which can be worked around today with a little work, and a proper X terminal). If this terminal-based workflow is going to thrive in the future, what will need to be modernized is the terminal.¹ So you heard it here first: if a new vim built atop a Lisp interpreter running on a new data-centric, mixed character-grid/HTML5-webview terminal emulator does not appear in the next 10 years, I'm on the job.² ¹ Some excellent musings on the subject: http://lubutu.com/idea/ivo http://lubutu.com/idea/ivo ² This would all be easier if I could love to learn Emacs, but Vim modal editing is a pernicious addiction.
- merlincorey 14y agoI heard you like Vim, but want an emacs-backend, without all the work. http://emacswiki.org/emacs/ViperMode http://emacswiki.org/emacs/ViperMode You're welcome :D
- jamesrcole 14y agoI haven't used it myself, but I've heard a number of people say that it's not really the same. I think their complaint was that it's a somewhat superficial emulation.
- Derbasti 14y agoEvil is better than Viper and Vimpulse in every way.
- Evbn 14y agoCan the Pyhton API do everything brainfu^Wvimscript can?
- jlgreco 14y agoYeah, to my knowledge. Basically it lets you execute Vim commands from python.