8 ms·
One of Neovim's capabilities that seems really promising is enabling rich GUI interfaces for an editor that does not simply emulate vim behaviour. An instance
by badosu 9y ago
One of Neovim's capabilities that seems really promising is enabling rich GUI interfaces for an editor that does not simply emulate vim behaviour.
An instance of this is Oni[0].
- https://github.com/onivim/oni https://github.com/onivim/oni
- sigi45 9y agoI was going to rant about this idea but it looks really good and not at all like gvim.
- baldfat 9y agoBut this looks just like a customized Vim in a terminal with what some may consider bloat. > Oni brings several IDE-like integrations to neovim: Quick Info Code Completion Syntax / Compilation Errors Fuzzy Finding Status Bar
- lsiebert 9y agoIt's not a terminal though, so you can get GUI features that terminal nvim can't do. Personally I use terminal vim not any sort of nvim (maybe I should change over but then I potentially have to maintain two sets of plugins, one for nvim and one for vim. ). No if you want to call this out, I'd call it out for the lack of features. This only supports code completion in JS and TypeScript. I have code completion plus snippets for a lot more then that with vim. Honestly if you want to wow me, someone should build a GUI configuration tool for neovim/vim. One big benefit of GUIs is that you can generally see all the possible settings with tool tips and explanations, and I can see that being useful for vimmers, especially if it did the right thing, like using ft-plugins to do filetype specific settings, instead of a bunch of one line autogroups based on file extension. Yes there are vim config generators, but the neovim api means you could programmatically query the current configuration and display it along with the options, meaning you could have interactive configuration modification.
- fmoralesc 9y ago> This only supports code completion in JS and TypeScript. I have code completion plus snippets for a lot more then that with vim. No, this only supports the extended features fro completion for those languages. It should use the simpler completion system for other languages, in which case you are using vim's support anyway.
- nerdponx 9y agoI've been wanting to do exactly this for a long time, for exactly the reasons you state.
- elkelk 9y agoYou'd be surprised, when I switched to nvim my plugins just worked.
- cstrahan 9y ago> maybe I should change over but then I potentially have to maintain two sets of plugins, one for nvim and one for vim I use this in my ~/.config/nvim/init.vim: set runtimepath^=~/.vim runtimepath+=~/.vim/after let &packpath = &runtimepath source ~/.vimrc That lets me directly use vim config from neovim. Then I set up an alias in my zsh profile: alias vim=nvim All of my plugins thus far have worked without a hitch (and I have a lot of configuration/plugins). If I ever run into problems, I can bail out by removing the alias (or for a one-off editing session, I can just run: $ command vim). You might give something like that a go.
- lsiebert 9y agotwo plugins failed until I installed https://github.com/neovim/python-client https://github.com/neovim/python-client Which seems to have fixed things.
- nerdponx 9y agoYou can literally use Neovim as the Sublime Text editing engine.
- joejoebob 9y agoIs there a plugin for this?
- lunixbochs 9y agohttps://github.com/lunixbochs/actualvim https://github.com/lunixbochs/actualvim It's not just "literally use Neovim as the editing engine", I've tried to make editing the text in "Sublime Mode" work too, including running Sublime plugins. Work in progress, but afaik the most complete Vim integration for an existing editor. Waiting on updates to both Neovim and Sublime Text to polish it a bit more. VSCodeVim is using it as a reference for some of their new work as well.
- joejoebob 9y agoThanks!
- coldtea 9y ago>But this looks just like a customized Vim in a terminal with what some may consider bloat But we can chose to ignore those "some", just like they can keep using whatever works for them.
- Sir_Cmpwn 9y agoNo no no no no. This is based on Electron and is a non-starter.
- badosu 9y agoI stick to this philosophy for many things, tracked for many months the more efficient GUIs for neovim (mainly neovim-qt, see full list at [0]). However I really wanted to have a little more interactivity (and visuals) than what the terminal can provide and so far Oni has delivered it good enough for me. That said, there are a lot of daily editing issues to be solved before it can be said battle-tested. [0]: https://github.com/neovim/neovim/wiki/Related-projects#gui https://github.com/neovim/neovim/wiki/Related-projects#gui
- derefr 9y agoHow would you feel about Electron projects if Electron was instead: 1. a single shared runtime install, installed transparently by the first thing to need it (similar to how the Adobe Air first-use experience worked), rather than a vendored dependency? 2. a shared VM that ran its apps in separate V8 execution contexts (like how browsers isolate tabs), but with a lot of shared resources so that each Electron app didn't end up with a GB of (mostly redundant) memory consumption? I find that most people don't object to HTML5 apps per se; they just object to the way Electron handles things. The above was going to be the strategy of Chrome's "app-only runtime" mode, until they just killed off Chrome Apps altogether. I still think it's a decent strategy, all-said.
- jackmott 9y agoI'd like electron if it was just a natively, AOT compiled rendering library.
- Sir_Cmpwn 9y agoI would feel marginally better but still hate it. I don't like the web as a platform anyway, especially not one for applications with cancerous amounts of JavaScript. HTML is not a platform for desktop applications. It shouldn't be a platform for almost anything.
- dguaraglia 9y agoI really, really want VSCode's Vim mode to be based on Neovim (they already do some kind of Neovim integration.) I wish I had more time during my weekends to collaborate on such a thing.
- jamesgeck0 9y agoIt's coming! From the VSCode Vim v0.10.0 path notes: > One more thing. I apologize for less work being done on the main repo. Much of my effort recently has gone into the neovim version of this extension (still in development).
- chillee 9y agoThe current work for this is being done here: https://github.com/chillee/vscodeneovim https://github.com/chillee/vscodeneovim
- tym0 9y agoSomeone is working on that: https://github.com/VSCodeVim/Vim/pull/1897 https://github.com/VSCodeVim/Vim/pull/1897
- jjrh 9y agoI wish someone would give this kind of love to emacs. emacs's gui is sufficient but really doesn't take advantage of any of the features a GUI offers.
- dpc_pw 9y agoI can't wait to make my code editor eat 2GB of RAM, like modern editors do, without sacrificing on Vim features.