231–240 of 271 posts
With all the supply chain attacks this last week, little hesitant to upgrade.
Earlier quoted context omitted.
I've been using Vim daily for 13 years and switched to NeoVim about a year of two ago. For me the main advantages over Vim are just the Lua scripting instead of Vimscript, its support for language servers, and better handling of terminals windows running inside Vim. However, I do still run visual studio in parallel for debugging. It's basically essential when dealing with console game development.
I just let AI handle any and all debugging at this point, haven't had an issue where AI couldn't find out what the problem was, finding a solution on the other hand is a hit or miss still.
Earlier quoted context omitted.
Doesn't seem like it if you can waste time learning all the keybinds just because you switched an editor, but also how does "can't do things since there are no plugins yet" rank higher vs "sometimes stops working" in importance?
It took me about 10 min to learn the keybindings. It does take longer to get familiar and efficient with them, but I wasn't a Vim master to begin with. (I can navigate efficiently and am proficient with a few combinations that I use the most, but that's about it.) > "can't do things since there are no plugins yet" Depending on what I am doing, I will probably go back to VSCode to get things done. Terminal editors are…
Your arguments here are valid, for a particular kind of person who values a particular kind of workflow.
Some of us would rather use vi than vscode. If you take away the plugin ecosystem, the core value is still there.
Earlier quoted context omitted.
I just let AI handle any and all debugging at this point, haven't had an issue where AI couldn't find out what the problem was, finding a solution on the other hand is a hit or miss still.
Can AI pause execution and step through the code line by line? Because that's what I think your parent comment is referring to.
Upgrading from 0.11 was relatively painless, except for nvim-treesitter, which pretty much became a new plugin. The previous version lives in the master branch, but doesn't support 0.12 at all, so you need to use the main branch when updating. Most of the previous features are replicable with new code, except for incremental selection. treesitter-modules[1] serves as a good bridge between old and new APIs. [1] https:…
Earlier quoted context omitted.
I've found Neovim to be remarkably stable, even when building from main.
You haven't been using the LSP API then. There have also been multiple breaking changes over the last five years, including breaking compatibility with established default vim keybindings.
I swapped to neovim and never looked back. I don't even have vscode, jetbrains or anything similar installed anymore. AI has made it so so easy to get into neovim and make anything work no matter how obscure it is. The biggest benefit for me which I haven't realized how good it is with tmux and the low low memory usage. I mean I can keep EVERY project I work on open, quickly switch and maintain. No more 10gb memory u…
I use neovim daily but am 100% sure I'm not even scratching the surface of its power. In fact I'm not even sure I'm using anything specific to the "neo" variant vs plain vim. I can do simple search/replace, page up/down, jump to character or delete x words, but I feel like I'm missing a lot to really take advantage of it. Is there a tutorial or guide people recommend to become more of a power user? The only plugin I…