We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS
No response
20240203-110809-5046fc22
Yes, and I updated the version box above to show the version of the nightly that I tried
running wezterm.run_child_process() works only if I open wezterm from another terminal, but if I open it from macos with spotlight it does not
{ key = "2", mods = "CMD", action = wezterm.action_callback(function(window, pane) wezterm.run_child_process({ "zellij", "-s", "joyous-triceratops", "action", "go-to-tab", "2", }) end), },
It is weird because if I run wezterm from another terminal it works perfectly fine, but not if I open it from spotlight.
The text was updated successfully, but these errors were encountered:
https://wezfurlong.org/wezterm/faq.html#im-on-macos-and-wezterm-cannot-find-things-in-my-path
Sorry, something went wrong.
No branches or pull requests
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
20240203-110809-5046fc22
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
running wezterm.run_child_process() works only if I open wezterm from another terminal, but if I open it from macos with spotlight it does not
To Reproduce
No response
Configuration
Expected Behavior
It is weird because if I run wezterm from another terminal it works perfectly fine, but not if I open it from spotlight.
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: