Repository navigation
Add history_back and history_forward focus navigation - #5743
dlamacchia wants to merge 1 commit into
Conversation
Track a per-client back/forward history of focus jumps across tabs and workspaces, observed from client shell snapshot transitions so every source of focus change is captured. Pane moves within a tab update the current entry instead of adding one, so stepping back returns to the exact pane that was left. The history is browser-style (a new jump discards forward entries), capped at 50 entries, kept in client memory only, and cleared when the endpoint reboots. Steps skip panes that no longer exist, and in-flight steps are not recorded as new jumps. Both actions are unset by default.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one): 1
Please check the settings in the CodeRabbit UI or the
 |
|
Hi @dlamacchia, thanks for your interest in contributing. Herdr does not accept unsolicited implementation pull requests from contributors who are not listed in The pull request author is not an approved contributor. If you encountered a reproducible bug, report the observed behavior through the bug issue template. A report does not reserve the work or authorize a pull request; accepted fixes are normally implemented by Herdr’s maintainer-controlled agents. Feature requests, behavior changes, and other proposals belong in GitHub Discussions. Do not open an issue merely to justify an implementation that was already written. If a maintainer explicitly wants this implementation, they can reopen the pull request. Reopening by anyone else will be closed again automatically. See https://github.com/herdrdev/herdr/blob/master/CONTRIBUTING.md for the contribution policy. |
Track a per-client back/forward history of focus jumps across tabs and workspaces, observed from client shell snapshot transitions so every source of focus change is captured. Pane moves within a tab update the current entry instead of adding one, so stepping back returns to the exact pane that was left.
The history is browser-style (a new jump discards forward entries), capped at 50 entries, kept in client memory only, and cleared when the endpoint reboots. Steps skip panes that no longer exist, and in-flight steps are not recorded as new jumps.
Both actions are unset by default.