4 ms·
I’ve felt similarly, and really wanted to switch to VSCode. But it gives each pane its own set of tabs, while Vim has a single set of “tabs” (buffers) and multi
by psadauskas 3y ago
I’ve felt similarly, and really wanted to switch to VSCode. But it gives each pane its own set of tabs, while Vim has a single set of “tabs” (buffers) and multiple panes within it.
I’ve been using N/Vim for 25 years, and even after trying for a week or two, I just can’t get comfortable with VSCode’s way of doing it.
https://github.com/microsoft/vscode/issues/143024 https://github.com/microsoft/vscode/issues/143024
- JeremyNT 3y agoI find the same. Vim has some core concepts that are unique and (for those of us who adopt them) very sticky. My entire career has been spent trying out IDEs every few years in hope of switching, dating back to Eclipse. I always try their vim modes too. But the reality is that the core editing experience in vim is so central to how I work that I can never manage it. I like features, and I have no love for arcane configuration of plugins. Yet to this day I've found nothing better for me than vim.