201–210 of 271 posts
Earlier quoted context omitted.
any chance you have a key sequence mapping that starts with esc? sounds like its waiting to see if you are gonna be pressing another key before timing out and do its thing
It happens randomly, which makes me think it's a bug.
Earlier quoted context omitted.
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…
Maybe try https://vim-adventures.com/
What’s the use case for editors when agents write the code?
The elephant in the room is that there's nothing quite like Cursor Tab. Copilot, Supermaven, Codecompanion, etc. don't even come close. As much as I want to use Neovim full time, I just can't walk away from Cursor Tab. I can live without Cursor Agent since I can just use Claude Code when I need an agent. Until something comparable for Neovim comes out, I just don't see how I can switch back. I would happily pay for t…
Earlier quoted context omitted.
Highlighted search/replace does this pretty well too.
Not really, it only does it for the first edit, while multiple cursors offer continuous feedback for all further besides, search/replace has extra toolbar and usually can't as easily select, for example, "current Identifier under cursor" if those are different, so it's worse before the first edit as well
Earlier quoted context omitted.
Not really, it only does it for the first edit, while multiple cursors offer continuous feedback for all further besides, search/replace has extra toolbar and usually can't as easily select, for example, "current Identifier under cursor" if those are different, so it's worse before the first edit as well
I'll have to try that out sometime. Never used multiple cursors. However, search/replace with vim/neovim isn't just the first edit either. It highlights all matches and shows you the proposed changes as you type as well. (It is probably a configurable thing).
You search for OLD, replace it with NWE, then notice the typo, delete 2 chars and type EW. How can search and replace help you here without searching for NWE anew?
Yeah, do try it out to at least see the difference
What’s the use case for editors when agents write the code?
Earlier quoted context omitted.
I'll have to try that out sometime. Never used multiple cursors. However, search/replace with vim/neovim isn't just the first edit either. It highlights all matches and shows you the proposed changes as you type as well. (It is probably a configurable thing).
How can it show proposed changes if search doesn't match anymore after edits? You search for OLD, replace it with NWE, then notice the typo, delete 2 chars and type EW. How can search and replace help you here without searching for NWE anew? Yeah, do try it out to at least see the difference
How does multiple cursors work anyway? How do you place them? By search? Is it used for anything other than working on matching text?
Earlier quoted context omitted.
Couldn't disagree more. Why move away from solid, mature build systems to something relatively fringe like zig. Sadly, this is the general trend with neovim in general: less focus on stability, more and more focus on shiny new things. If I didn't have an nvim config that I'm used to I would have switched to plain vim ages ago.
I've found Neovim to be remarkably stable, even when building from main.
Earlier quoted context omitted.
Maybe when `:!` works the way vi does and POSIX says it must. Just kidding, that will never happen.
Preach! I tried to point this out in the Neovim discord once and was basically told to pound sand. Very frustrating. My initial issue: https://github.com/neovim/neovim/issues/35258 The interactive issue: https://github.com/neovim/neovim/issues/1496 I really just want a, do the old thing setting. It was simpler and worked better.
[0] https://gist.github.com/Konfekt/8e484af2955a0c7bfe82114df683...