-
-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
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
Wezterm crashes when trying to start tmux -CC
#4904
Labels
bug
Something isn't working
Comments
MacOS report (didn't fit into previous comment)
|
Duplicate of #3223 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
N/A
WezTerm version
wezterm 20240128-202157-1e552d76
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
No
Describe the bug
Freshly installed (via homebrew) Wezterm with no config crashes when running
tmux -CC
.I didn't try the nightly explicitly. The version I used was very recent and might already be the nightly.
To Reproduce
Configuration
No configuration file
Expected Behavior
No crash. Perhaps wezterm should report that it doesn't support tmux's control mode.
Logs
Debug Overlay
wezterm version: 20240128-202157-1e552d76 aarch64-apple-darwin
Window Environment: macOS 14.2.1 (23C71)
OpenGL: Apple M2 Pro 4.1 Metal - 88
Enter lua statements or expressions and hit Enter.
Press ESC or CTRL-D to exit
**Wezterm output and panic**
Anything else?
Cc: #336
I'm not sure if this problem is specific to
tmux -CC
, which apparently isn't supposed to actually work yet, or is indicative of a larger problem. In any case,The text was updated successfully, but these errors were encountered: