MacOS上的TMUX在ITERM2或终端中打开时退出
我无法使用空的tmux
在ITERM2或终端打开,使用空tmux.conf
。从跑步会话中拆分窗口也会失败。 (不是我再有任何跑步会议。)在iterm2中,我得到了三个可能的响应之一;终端只有两个。 (我还尝试了tmux.conf tmux ships的示例。相同的结果)。
iterm2中
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] Term2 3.4.15
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] tmux -f ./none.conf
^[[>0;95;0c^[P>|iTerm2 3.4.15^[\[exited]
在终端中的
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] tmux -f ./none.conf
^[[>1;95;0c[exited]
I'm unable to open tmux
in either iTerm2 or Terminal with an empty tmux.conf
. Splitting windows from a running sessions also fails. (Not that I have any running sessions any more.) In iTerm2 I get one of three possible responses; with Terminal only two. (I've also tried the example tmux.conf that tmux ships with. Same results).
in iTerm2
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] Term2 3.4.15
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] tmux -f ./none.conf
^[[>0;95;0c^[P>|iTerm2 3.4.15^[\[exited]
in Terminal
[jayed@merlot ~/jank] tmux -f ./none.conf
[exited]
[jayed@merlot ~/jank] tmux -f ./none.conf
^[[>1;95;0c[exited]
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我将重新提到 @Mauricio-poppe。我在TMUX运行时进行了
BREW升级
,重新打开TMUX将导致一些铃铛字符,并在我的提示符中输出term2 3.4.15
输出。为了解决这个问题,我跑了:
现在TMUX按预期工作。
我猜想构建/安装需要访问TMUX仍在运行时锁定的东西。
I'm going to re-iterate @mauricio-poppe mentioned. I did a
brew upgrade
while tmux was running, and reopening tmux would result in some bell characters andTerm2 3.4.15
output in my prompt.To fix this, I ran:
Now tmux works as expected.
I'm guessing the build/install needed access to something that was locked open while tmux was still running.
我会留下来可能会帮助某人。
这与2022年6月9日推到自制的TMUX 3.3A升级有关。回到3.3解决了我的问题。
我不知道具体问题是什么。
I'll leave this up to maybe help someone.
This has to do with the tmux 3.3a upgrade pushed to homebrew on 9 JUN 2022. Rolling back to 3.3 solved my problem.
I don't know what the specific issue is.