Repository navigation
Replies: 6 comments 3 replies
|
I have a similar workflow. Had to roll back herdr due to the breaking change. Would love a way to opt out of the changed link behaviour |
|
I can see the intent of @JJLiebig 's change - basically make the config option However I believe it accidentally couples the different kinds of mouse events together:
I think a maintainable solution would be to have a config option for each category of mouse events. I propose adding one in |
|
Similar flow here: Ghostty on macOS, SSH to a Linux host, herdr 0.9.5. With capture on, an OSC 8 link printed in a pane ( A separate, related point for that mode: plain-text URLs that wrap across pane rows. Shift+Cmd-click on a wrapped URL opens only the part on the first row, because my local terminal sees each row separately. herdr treats a wrapped URL as one link for its own Ctrl-click, but that opens it on the host running herdr. It would help if URLs herdr recognizes reached the local terminal as whole links. Related: #2780 (open links on the client in remote mode; its first option was handing the URL to the client terminal). |
|
This is terrible, it makes Herdr unusable for me. I am downgrading to the version before they messed this up, and staying there until they fix it, or I find another solution |
|
Consolidating discussion in: #5272 Very happy to hear feedback about that |
|
Could you try JJ’s test build from PR #5457 (commit For the SSH workflows here, please check that Download choices and safe test-session instructions are on the PR. This is experimental, not a release. Keep mouse capture enabled; both client and server need this build. For terminal → SSH → Herdr, run the host artifact in the SSH shell rather than changing your local terminal. Please leave your terminal/version, setup, gesture, and result on issue #5272 so the test feedback stays together. |
Uh oh!
There was an error while loading. Please reload this page.
idea / problem
My workflow is local terminal → SSH → remote host → Herdr → Pi.
Pi can display OSC8 hyperlinks using
vscode://andwinscp-sftp://. My local terminal handles Ctrl-click and opens VS Code or WinSCP on my local computer.Before 0.9.4, these links worked alongside Herdr’s mouse controls. Since the change in #5064, application links no longer open with mouse capture enabled.
I tested
ui.mouse_capture = false, it restores link activation, but also disables Herdr’s mouse controls for tabs, menus, and split resizing.Related: #5272 acknowledges this tradeoff as intentional. Discussion #1959 also mentions the 0.9.4 change.
requested change
Allow native OSC8 hyperlink passthrough to be enabled independently of Herdr’s mouse controls.
The current plugin-first behavior could remain the default. An opt-in terminal-native mode would preserve tab clicks, menus, and split resizing while allowing the connecting terminal to handle hyperlink activation.
why you want this
I regularly use both herdr’s mouse navigation and clickable file links. These worked together before 0.9.4; now I must choose between them.
Because I connect over SSH, the links need to reach my local terminal and its registered application handlers. Launching VS Code or WinSCP on the remote host through a herdr plugin would not restore this workflow.
I want an opt-in way to recover the previous behavior without removing plugin precedence for users who need it.
All reactions