Mac Julia binary open with does not work

Open
#3,138 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
julia, macos, zsh
Domain
cli, desktop

Research direction

The report provides no implementation file or test; start by reproducing the macOS “Open With” launch of /Applications/Julia-1.9.app/Contents/Resources/Julia/bin in Warp and compare it with Terminal and iTerm2. Done means the Julia application starts in Warp through Open With, while Julia still runs when launched from an existing Warp session.

Written by the indexing model from the issue text.

Description

area:performance area:shell-terminal area:warp-drive bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

I can not get the Julia application to open in Warp when I double click Julia to open it. By default, it opens in the macOS terminal with no issues.

To reproduce

File path /Applications/Julia-1.9.app/Contents/Resources/Julia/bin
I used the open with option in an effort to have the Julia application binary open in Warp rather than the default macOS terminal. I verified that this would work by changing it to open in the iTerm2 terminal just prior to submitting this issue. Therefore it appears that is a flaw in Warp
The screenshot shows what happens. Warp just comes up and "sits there" but Julia never starts.

Expected behavior

I expect to see Julia running in Warp. NOTE: I can call Julia from Warp if I open Warp first

Screenshots
Screenshot 2023-05-27 at 8 26 45 AM
Operating system

MacOS

Operating system and version

Ventura 13.3.1 (a)

Shell Version

zsh 5.9 (x86_64-apple-darwin22.0

Current Warp version

v0.2023.05.23.08.05.stable_00

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

today

Additional context

No response

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

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

None

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.