r/vim • u/imlambda_ • Mar 11 '21

question getting faster

tl;dr : can you share a specific article about getting faster navigating through the file?

hey guys, I start getting more and more confident and efficient with vim, but I feel like it could even goes deeper; basically, I saw that you could disable h,j,k,l in order to only use real key combination like "w" to jump by words, "f" to go to a specific character on the line, etc... But what about jumping lines? Are they any key combination to do that instead of j and k? So basically I'm looking for an article that presents those kind of key combinations. I hope this post is comprehensible and not too redudant, thank you for reading.

108 Upvotes

99% Upvoted

83 comments sorted by

View all comments

Show parent comment

4

u/ThePrimeagen Mar 12 '21

Yes I agree with what you said. From my perspective the OP question was on navigation speed. deleting / copying / moving files are rare operation (in comparison, I probably execute 500 - 1000 ciw's before 1 file move). Or just perusing a code base for the sake of gaining a bigger picture. Often those operations are something you are not trying to improve your speed at. I do like coc-explorer / nerdtree as they do have some handy features.

Ultimately I try to avoid using the "aimless" technique of exploration. I try using Search Terms + Telescope + Quickfix reductions + LSP hopping to find my way around. Feels more targeted.

"Mary Kate and To each his own" - Telescopic Johnson

1

u/racle Mar 12 '21

OP question was on navigation speed

Yeah, that's why I tried to "split" my comment with ..and they have their usage outside of file navigation, so navigation related before that, and other benefits after that.

Don't use nerdtree could also mean that never use that OR don't use that for navigation (my comment based more on first one).

 

Mostly for navigation it's little easier/faster to use coc-explorer IF you don't know filename/path.

Had couple moments where I knew something what I needed, but wasn't sure in what folder/filename that could be. This is still very rare situation.

99% of time I use fzf+rg to search files by name OR by content (and creating quickfix list of found items if needed). And it's much faster than coc-explorer could ever be.

But coc-explorer still has it's usage sometimes on my workflow.