4 ms·
I find being good at vim makes exploration much easier though. Being able to use Ag to populate a quick fix list is way faster for me than ctrl-f plus clicking
by GhostVII 6y ago
I find being good at vim makes exploration much easier though. Being able to use Ag to populate a quick fix list is way faster for me than ctrl-f plus clicking through every option. And being able to go up and down the movement stack let's me retrace how I navigated to where I am right now, in a way that isn't possible in many editors. Tools like just searching through open buffers let me use search in large codebases without having to wait forever for results. So for me being good at an editor is more than just being able to make fast edits (although that's definitely a benefit too).
And even if I only saved a few minutes a day, over several years that is a lot of time saved, without much investment. It's really easy to get started with vim, get comfortable with the basics in an hour or two, and then just get better by using it every day. Then you can slowly introduce features that save you time. Just setting up fzf and ag has probably saved me several minutes a day vs. using vscode search.
- brandonmenc 6y ago> Tools like just searching through open buffers let me use search in large codebases without having to wait forever for results. Is there an IDE that does not have this feature?
- plorkyeran 6y agoIf Xcode has an option to search only in open files I've never found it.
- TinkersW 6y agoIt sounds like you have no real experience with a good IDE, VS has way better search tools than "ctrl f"
- RandoHolmes 6y agoI'm a vim user so I mostly agree with you, but I'd like to point out that it's the entire OS that makes dealing with codebases easier. It's a point that a lot of IDE users miss. I have grep and awk at my fingertips, you don't.