You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240922-151228-2b76c63b
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
When starting WezTerm by issuing the command
wezterm start --always-new-process
(or even just wezterm start, and also if using wezterm-gui), the window that opens is in the background:
CleanShot.2024-09-28.at.11.53.00.mp4
This happens whether issuing wezterm start from another terminal, or via any other way of running a command (a shell script inside a Keyboard Maestro macro, in my case). The only way to start WezTerm in the foreground is to open the WezTerm.app.
To Reproduce
Open the macOS built-in Terminal app.
Run
wezterm start --always-new-process
Configuration
no config
Expected Behavior
A new WezTerm GUI app instance should appear, active and in front of my existing windows (as if I had launched the WezTerm.app in the GUI)
I came across something similar recently in neovide/neovide#2330, and the resolution there – using the deprecated -[NSApplication activateIgnoringOtherApps:] API – might be applicable here as well.
In fact, this issue with WezTerm came up while trying to set it up as a wrapper for neovim. I'd be interested in any workarounds for a background shell script running something like
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20240922-151228-2b76c63b
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
When starting
WezTerm
by issuing the command(or even just
wezterm start
, and also if usingwezterm-gui
), the window that opens is in the background:CleanShot.2024-09-28.at.11.53.00.mp4
This happens whether issuing
wezterm start
from another terminal, or via any other way of running a command (a shell script inside a Keyboard Maestro macro, in my case). The only way to start WezTerm in the foreground is to open theWezTerm.app
.To Reproduce
Open the macOS built-in
Terminal
app.Run
Configuration
no config
Expected Behavior
A new
WezTerm
GUI app instance should appear, active and in front of my existing windows (as if I had launched theWezTerm.app
in the GUI)Logs
Anything else?
I came across something similar recently in neovide/neovide#2330, and the resolution there – using the deprecated
-[NSApplication activateIgnoringOtherApps:]
API – might be applicable here as well.In fact, this issue with WezTerm came up while trying to set it up as a wrapper for
neovim
. I'd be interested in any workarounds for a background shell script running something likeand having that WezTerm window appear in the foreground.
The text was updated successfully, but these errors were encountered: