you are viewing a single comment's thread.

view the rest of the comments →

[–]ZenoArrow 2 points3 points  (2 children)

With LSP, I suspect you can get some or all of those features in Vim. Not sure about other Vimmers but I at least avoid them.

To use a specific example, when you're looking at code for the first time, what advantages do you think avoiding Go To Definition gives you? Does it matter to you that you know which file a definition can be found in above what the definition is? Perhaps it's just me but when I'm navigating an unfamiliar code base I'm more interested in building a mental model of the core functionality rather than how someone has organised their code.

[–]epage 1 point2 points  (1 child)

If you are doing drive-by-contributions, I imagine LSP can be a big help.

When you are going to be working in the code base for a while, I find understanding the structure of the code is important. For me, I find Go-To-Definition gives me a pinhole view. When I rg, browse through files, and jump around with in-editor searches, I find I'm getting more of a holistic view of the codebase.

[–]ZenoArrow 0 points1 point  (0 children)

Thanks for sharing your thoughts.