Skip to content

Latest commit

Β 

History

History
49 lines (33 loc) Β· 2.15 KB

File metadata and controls

49 lines (33 loc) Β· 2.15 KB

VSCode Jump History

δΈ­ζ–‡ README

Automatically records your source-code jump stack triggered by Ctrl + Click or Go to Definition (F12), and displays it in the left Explorer sidebar.

πŸš€ Quick Links

✨ Features

  • Automatically tracks cross-file / cross-location jumps for Definition, Reference, Implementation, Type Definition, and Declaration
  • Displays the jump path as a nested stack in the Explorer Jump History view
  • Click any history node to jump back to its location instantly
  • One-click clear history
  • Special handling for Go language, allowing URL-related package import jumps to be recorded

πŸ›  Usage

  1. Open this project in VSCode
  2. Press F5 to launch the Extension Host for testing
  3. In the test window, open any code project and use Ctrl + Click or F12 to jump to definitions
  4. The Jump History panel in the left Explorer will automatically record the jump chain

πŸ“ Project Structure

.
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ extension.ts           # Main extension entry: listens to editor changes and detects jumps
β”‚   └── historyTreeProvider.ts # TreeView data provider: renders the jump stack
β”œβ”€β”€ out/                       # Compilation output
β”œβ”€β”€ package.json               # Extension manifest
└── tsconfig.json              # TypeScript configuration

πŸ”¬ How It Works

The extension listens to onDidChangeActiveTextEditor and onDidChangeTextEditorSelection events. After detecting a significant location change, it uses built-in VSCode providers such as vscode.executeDefinitionProvider to infer whether the change was caused by a symbol navigation action. If so, the from β†’ to record is pushed onto the stack and rendered in the sidebar.

πŸ“ Credits

  • This project was written using kimi-cli & Qwen Code CLI.
  • The vast majority of the code was generated by LLM β€” a product of Vibe Coding.

πŸ“œ License

MIT Β© conglinyizhi