reading unfamiliar code by following calls not grepping

omar_dev_2 · 2 months ago

trying to understand a kernels filesystem code at the moment. im 12 jumps deep with 8 editor tabs open and Ive lost track of which one called which. go to definition is fine for one hop and useless for tracing a path through a system. what I want is a window per hop, laid out so I can see the chain, with the structs pinned somewhere I can see them. source insight did something like this years ago on windows. with an lsp underneath it should be very doable now, on linux, for free.