61–70 of 112 posts
Earlier quoted context omitted.
That is the reason why I moved from eMacs to neovim. Emacs on itself is amazing piece of software, but I had to fight my way to setup vim binding on everything. With neovim you just get that by default. Everything is thought around that.
In what scenarios were you reaching for your mouse within emacs?
I have used VSCode-Neovim on OSX since roughly NVIM v0.5. It is quite simply the best vim environment I've ever used and I've used quite a few. I date myself back to vim, back to vi and even to TECO. I pair this setup with the clangd LSP extension which makes it even more awesome. This is editor heaven. However it isn't perfect, yet. Command mode is still a work in progress and I use command mode a lot. Navigation wi…
I reverted to Vim after trying NeoVim for a few weeks simply because a lot of Vim defaults had to be chased-down and configured just to get basic Vim features in NeoVim. NeoVim also requires messing with a ton of config files compared with Vim so no thanks.
I've only got one config file for neovim that still works for vim, so your info on that is just plain wrong.
What defaults did you have difficulty with? All my settings were mostly the same.
I reverted to Vim after trying NeoVim for a few weeks simply because a lot of Vim defaults had to be chased-down and configured just to get basic Vim features in NeoVim. NeoVim also requires messing with a ton of config files compared with Vim so no thanks.
Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
I do now have memorized some mix of vim and vscode keybindings, but to me it's worth it. I'm not at 100% keyboard navigation because in some cases I've burned 5-10 minutes looking up a shortcut, repeatedly 1/mo for 3 months. After so many (overly) spaced repetitions, I recognize the shortcut isn't worth memorizing. > Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems…
Earlier quoted context omitted.
Been using it for a couple of years. No problems. You don't get the "absolute fullest" (neo)vim experience because you don't get the buffers/panes like you do in nvim though.
I actually do use pane commands from time to time. ctrl-w s : will split horizontally ctrl-w v : will split vertically Commands work, and I just tested buffers specifically. I can type :buffers and I see a list. I was able to get vscode to switch tabs with :b 209 (I don't normally inspect buffers this way, but it's integrated and it works).
My biggest complaint is probably that it doesn't support overlay or popup windows, which makes it impossible to use plugins like WhichKey[0] and such, which I like on normal neovim because I'm a scrub and don't know vim hotkeys by heart 0: https://github.com/folke/which-key.nvim
Limiting this cheatsheet to just one side of an A4 sheet kept it usable and forced me to rewrite it every so often - every next iteration leaving off all the commands I had been checking back often enough for that they had finally stuck.
Completely unsolicited, but hopefully useful advise nevertheless :)
Earlier quoted context omitted.
I actually do use pane commands from time to time. ctrl-w s : will split horizontally ctrl-w v : will split vertically Commands work, and I just tested buffers specifically. I can type :buffers and I see a list. I was able to get vscode to switch tabs with :b 209 (I don't normally inspect buffers this way, but it's integrated and it works).
Do :sp and :vsp work?
Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
> Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems), you still need to resolve to using the mouse/Tabbing to actually install the plugin itself. Sounds like a minor annoyance at best... Where vim-mode is important to me is editing and navigating code, not when installing plugins...