Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Oni: Modern Modal Editing – Powered by Neovim

github.com

Post reply on HN
Print view View original

111–115 of 115 posts

Re: Oni: Modern Modal Editing – Powered by Neovim

#111

Post by kanbannoman »

gnulinux wrote: post #67
scrollaway wrote: post #47

Earlier quoted context omitted.

Urgh, this is so infuriating. Oni looks fantastic if it can deliver on what it does, but the infuriating part really is VSCode in all this. Code is a great editor/IDE and has a huge amount of development backing and now a pretty large market share as well, which means inertia. But the vim bindings for it are just garbage . They are slow, make the editor feel sluggish, they don't work "quite right", etc. No kidding th…

How does VSCode vim plugins compared to evil-mode of emacs?

the vscodevim plugin still has problems with things like scrolling (c-e, c-y, c-d, c-u) and is missing ex commands. Evil is more comprehensive

Re: Oni: Modern Modal Editing – Powered by Neovim

#112

Post by cellshade »

ubercore wrote: post #107
jakecopp wrote: post #61

Earlier quoted context omitted.

How does VSCode Vim bindings compare to Vintage mode in Sublime? I like the idea of Oni, but I also love that Sublime is native (I'm already running FF Quantum, I can't burn too much more battery!). I know Sublime's Vim keybindings aren't that complete.

I've found VSCode Vim bindings _really_ buggy. Sometimes non-responsive to the escape key until I press it a few times, sometimes it will kill highlighting of code blocks until I switch modes, sometimes enters ` ` in the source code instead of tab when I press the tab button. I still use it, because I've used modal editors for so long and I like everything else about VSCode, but the vim bindings are my biggest point…

What platform are you on? I've experienced no major issues with the vscode vim plugin on Mac or Windows.

The escape key issue you mentioned was the only problem I've also had, but it's due to conflicting keybinds between the vim plugin and the vscode bindings for dismissing notifications and context help. I rebound all of those to shift-esc (and I believe the plugin's bindings now do this by default) and the problem went away.

Re: Oni: Modern Modal Editing – Powered by Neovim

#113

Post by cellshade »

kanbannoman wrote: post #111
gnulinux wrote: post #67

Earlier quoted context omitted.

How does VSCode vim plugins compared to evil-mode of emacs?

the vscodevim plugin still has problems with things like scrolling (c-e, c-y, c-d, c-u) and is missing ex commands. Evil is more comprehensive

The slow scrolling key-repeat issue was recently fixed.

Re: Oni: Modern Modal Editing – Powered by Neovim

#114

Post by k_ »

toxik wrote: post #73
ComputerGuru wrote: post #66

Earlier quoted context omitted.

It’s a valid point. Lots of people use vim for its sheer speed, which you throw out with the bath water when switch to electron.

I haven’t tried the app yet but it seems that this is not true for this editor as NeoVim is the backend, not JavaScript.

1.5G for a fresh startup with no files open is unacceptable when looking for a lightweight editor. That's what made me go back to vim; my previous laptop with 4G RAM couldn't handle vscode + a browser without going out of RAM. I had some hopes for oni but so far it doesn't solve any issue I have either with nvim or with vscode.

Re: Oni: Modern Modal Editing – Powered by Neovim

#115

Post by ubercore »

cellshade wrote: post #112
ubercore wrote: post #107

Earlier quoted context omitted.

I've found VSCode Vim bindings _really_ buggy. Sometimes non-responsive to the escape key until I press it a few times, sometimes it will kill highlighting of code blocks until I switch modes, sometimes enters ` ` in the source code instead of tab when I press the tab button. I still use it, because I've used modal editors for so long and I like everything else about VSCode, but the vim bindings are my biggest point…

What platform are you on? I've experienced no major issues with the vscode vim plugin on Mac or Windows. The escape key issue you mentioned was the only problem I've also had, but it's due to conflicting keybinds between the vim plugin and the vscode bindings for dismissing notifications and context help. I rebound all of those to shift-esc (and I believe the plugin's bindings now do this by default) and the problem…

I'll have to check out the key bindings, thanks for the tip. This is on OS X (High Sierra)
Post reply on HN