Replies: 1 comment
|
The latest frontier models (two most popular ones) are giving these local file links much more often than other models so it's becoming more painful that this doesn't work in Herdr. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What
Cmd-click on local file paths inside Herdr panes does not open the file in an editor or Finder, even though Cmd-click on
http:///https://URLs works correctly since #307.In iTerm2 without Herdr, Cmd-clicking a file path like
src/main/java/App.javaor/Users/me/project/README.mdopens the file in the configured editor (Semantic History). After switching to Herdr, this capability is lost because the outer terminal can no longer detect file paths in Herdr's rendered output.Current behavior
https://github.com/...src/main/java/App.java./README.md/absolute/path/to/file.ts:42Expected behavior
Cmd-click on a visible local file path opens the file in the user's configured editor or system default handler, similar to how URL clicks already work. Ideally this would support:
/Users/me/project/file.ts)src/app.ts,./README.md)file.ts:42,file.ts:42:10)Context
Terminal multiplexers sit between the shell and the host terminal, so host-level features like iTerm2 Semantic History cannot detect file paths in the multiplexer's rendered output. Since Herdr already implements its own Cmd-click URL detection (#307), extending the same mechanism to recognize file paths would restore this workflow without requiring
mouse_capture = false.Looking at the source,
safe_web_urlinsrc/app/actions.rs:1679currently gates clicks tohttp:///https://only, andurl_at_pane_cellonly extracts URL-shaped text. The pane's working directory is already available viaforeground_cwd(#345), so resolving relative paths should be feasible.This is a common pain point for developers who use Cmd-click heavily to navigate compiler errors, test failures, and grep output.
Environment
All reactions