apple script returns “stable” and not “warp” as application name

Open
#5,143 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No repository file, test, or entry point is mentioned. Reproduce the AppleScript using System Events on macOS 14.5 with Warp v0.2024.07.16.08.02.stable_02, then trace where the application process name is defined or exposed; the issue is done when the frontmost process reports Warp rather than stable.

Written by the indexing model from the issue text.

Description

bug needs-info ready-to-implement triaged
Dupe Check
Describe the bug

To adjust the window size, I retrieve the name of the app in the Apple Script. The result I get is “stable”

To reproduce

Warp is the frontmost window. I call up the script using a keyboard shortcut.

tell application "System Events"
    set frontApp to name of first application process whose frontmost is true
end tell

tell application "Keyboard Maestro Engine"
    setvariable "FrontAppName" to frontApp
end tell
Expected behavior

I expect that the variable "FrontAppName" is "Warp" and not "stable". Or maybe "Warp stable"

Screenshots

No response

Operating system

MacOS

Operating system and version

macOS 14.5 Sonoma

Shell Version

No response

Current Warp version

v0.2024.07.16.08.02.stable_02

Regression

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

Recent working Warp date

No response

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:b9d78064-c89e-4973-b153-5178a31ee54e

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.