Unable to follow links/paths via the "global window hotkey" instance

Open
#1,863 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, rust
Domain
desktop

Research direction

Reproduce the issue using a macOS global hotkey window and the reported zsh command output, then trace the link and path handling for that window versus a regular Warp window. Done means clicking links opens the browser and clicking paths opens the configured application or code editor in the global hotkey instance.

Written by the indexing model from the issue text.

Description

area:settings-keybindings area:window-tabs-panes bug needs-info ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

Clicking on links/paths (for example eslint outputs) does not open the default app/code editor or the browser in case of links.

If I open the a regular Warp window it works just fine.

To Reproduce
  1. Setup a "global hotkey window"
  2. Open via desired shortcut (CMD + F3 in my case)
  3. Run command which logs out some proper links/paths to the terminal (eslint in my case)
  4. Click on Paths/Links inside the command output
  5. Nothing is happening :(
Expected behaviour

The "global hotkey window" instance should behave the same as a regular Warp app window and open links/paths in the defined applications.

Screenshots

No response

Operating System

MacOS

OS Version

12.6

Shell Version

zsh 5.8.1 (x86_64-apple-darwin21.0)

Warp Version

v0.2022.09.13.08.15.stable_03

Additional context

No response

Does this block you from using Warp daily?

No

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

No response

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

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.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.