Something I got used to in Eclipse was the ability to set bookmarks on multiple files and then navigate to them by clicking on them in a master list.
I would use this technique a lot when exploring a codebase that didn’t have symbol-references handy (such as jsp files, etc.)… in order to “trace” the flow of an app from configuration, through the controller, then to the bean or models, then to the view – I’d bookmark each context switch. Then after verifying/understanding the code, I could easily “unwind” the stack back up to inspect the next function.
An alternative would be to load a log file such that you could see the stacktrace in a buffer and click on any relative path files with line numbers and the text editor would open them on that line (such as in emacs). But I like the bookmarks across files idea better as it’s more flexible than a stacktrace and allows paths outside the stack to be ‘traced’ by hand ( yml configs -> ruby files -> javascript files , etc.), yet keep all these marks in their proper sequence.
Oh, and eclipse has a capability to add text to the mark so that you can describe it in the list.