dkogan / dkogan/xcscope.el

navigating function call hierarchy

Open
#3 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Emacs Lisp
Stars
122
Forks
27
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the cscope-pop-mark command and the existing call-stack navigation entry points. Define the expected backward and forward traversal behavior for the call chain, then verify that navigating in either direction preserves the relevant marks and does not lose history.

Written by the indexing model from the issue text.

Assessment

Tech stack
emacs-lisp
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.