navigating function call hierarchy

[anupamk]

while tracing a function call flow, we can go up the call-stack via the "cscope-pop-mark", once that is done, the popped mark is lost.

it would be nice if we could have a 'queue' kind of semantics where the call chain can be traversed backwards and forwards as well.

[dkogan]

Anupam Kapoor notifications@github.com writes:

while tracing a function call flow, we can go up the call-stack via
the "cscope-pop-mark", once that is done, the popped mark is lost.

it would be nice if we could have a 'queue' kind of semantics where
the call chain can be traversed backwards and forwards as well.

Hi.

Thanks for the suggestion. Currently the plain emacs mark ring stores
all the locations too, so none of the positions are lost (unless I have
a bug, of course). I agree this isn't ideal, and I'll think about ways
to improve it.

[anupamk]

Currently the plain emacs mark ring stores all the locations too, so none of the positions are lost...

hmm, i was under the impression that the emacs-marker-ring doesn't cross buffer boundaries i.e. as i navigate within a file, i can C-u C-SPC, to some previous position within the same file. might be mistaken though.

thank you
kind regards
anupam

[dkogan]

OK; you're right. Emacs does have some global mark functions, and maybe they're useful here, but I need to sit down and think about this. I vaguely wanted something better in this area before, but haven't yet tried to think about what. Maybe simply adding a forward complement to cscope-pop-mark is enough.