3 ms·

I do think I might prefer the approach of the asymptotic of development approaching vscode features with a base in pure Vim rather than the asymptotic approachi

I do think I might prefer the approach of the asymptotic of development approaching vscode features with a base in pure Vim rather than the asymptotic approaching full Vim compatibility within vscode, and so I really want to like Oni. What immediately struck me as "this project is not ready to use to actually code in" was trying to scroll with my Macbook's touchpad and it working pretty awfully. It seems like an obvious enough issue that it _has_ to be being worked in, but maybe not and I should report it.

badosu 9y ago
This has been an issue for some time, tracked in (https://github.com/onivim/oni/issues/1568 https://github.com/onivim/oni/issues/1568) and (https://github.com/onivim/oni/issues/405 https://github.com/onivim/oni/issues/405). Unfortunately is not an easy task to accomplish at the moment, due to the way vim scrolling is tied with the terminal approach (line by line), does not seem as a hard block though and hopefully can be improved. Since most of the time you are scrolling with keybindings when using vim this may not be as big of an issue for most vim users (I never had issues in my experience), but certainly desirable to fix as it's a dealbreaker some.
pault 9y ago
The main issue preventing smooth scrolling is it will require each split to be an independent neovim instance, which is (in my opinion) not quite as nice as native splits. There is a feature in development that does use a separate view for each split and smooth scrolling is possible if you are willing to give up your native splits. In practice I haven't noticed it because I don't use the mouse for scrolling.