NeoVim + language servers + global search with rg + a bunch of keyboard shortcuts: - gd = go to definition - gr = open a hovering window filled with references to symbol This is enough to get through every codebase I've yet encountered (Go, Typescript, Python, Java, C++). I also like to use and in vim which allows you to jump between the most recently viewed locations. For keeping context, I just write everything dow…
Are those keyboard shortcuts part of the LSP server?
Ask HN: How Do You Navigate Code?
21–30 of 39 posts
Re: Ask HN: How Do You Navigate Code?
#22Take some rough notes on a google doc / gedit so that I don't forget paths that I've explored previously
Re: Ask HN: How Do You Navigate Code?
#23Re: Ask HN: How Do You Navigate Code?
#24run strace or ltrace on it;
grep: works better with editor assistance, such as emacs M-x grep;
write documentation for it;
factor out parts of it;
Re: Ask HN: How Do You Navigate Code?
#25NeoVim + language servers + global search with rg + a bunch of keyboard shortcuts: - gd = go to definition - gr = open a hovering window filled with references to symbol This is enough to get through every codebase I've yet encountered (Go, Typescript, Python, Java, C++). I also like to use and in vim which allows you to jump between the most recently viewed locations. For keeping context, I just write everything dow…
Are those keyboard shortcuts part of the LSP server?
nnore gd :LspGoToDefinition
...or something like that. I haven't touched the config in a few months.Re: Ask HN: How Do You Navigate Code?
#26In the old days when I did more Java dev, I used Eclipse to view where things are defined and find usages.
Re: Ask HN: How Do You Navigate Code?
#27I use VSCode and mostly navigate via: F12: Go to definition Shift+F12: Go to usages Ctrl+-: Go back Ctrl+Shift+-: Go forward Once you get used to it, it's as easy as browsing the web. Since I started using VSCode I did not have to work with codebases that were complex enough to make these features valuable but some VSCode language extensions support tree views of call hierarchies and type hierarchies. Here's the docu…
What version of VScode are you using?
Re: Ask HN: How Do You Navigate Code?
#28Otherwise, searches for file names and contextual links, usages etc.
Re: Ask HN: How Do You Navigate Code?
#29Re: Ask HN: How Do You Navigate Code?
#30I use VSCode and mostly navigate via: F12: Go to definition Shift+F12: Go to usages Ctrl+-: Go back Ctrl+Shift+-: Go forward Once you get used to it, it's as easy as browsing the web. Since I started using VSCode I did not have to work with codebases that were complex enough to make these features valuable but some VSCode language extensions support tree views of call hierarchies and type hierarchies. Here's the docu…
Ctrl+- is reduce font size Ctrl+Shift+- is a no-op What version of VScode are you using?
I guess Ctrl+Shift+- is a no op if you haven't first gone back.