-
Notifications
You must be signed in to change notification settings - Fork 79
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
Cannot terminate connected session #165
Comments
Hi @noctivityinc! I might misunderstood you, but a tmux client can be disconnected with |
Yes I’ve tried all those combinations to no avail. Any ideas?
…On Tue, Nov 28, 2023 at 12:26 PM Sergei Aleksandrovich < ***@***.***> wrote:
Hi @noctivityinc <https://github.com/noctivityinc>!
I might misunderstood you, but a tmux client can be disconnected with
Ctrl+b and then d, not with Ctrl+b+d. Ctrl+b is a default tmux command
prefix and it can vary depending on your tmux configuration.
—
Reply to this email directly, view it on GitHub
<#165 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATIAWV43L2J54EMWRSPL3YGYNGDAVCNFSM6AAAAAA753ZWWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQGM2DQMBZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I'd recommend checking if the prefix key is redefined in your |
Ok than you!
…On Dec 1, 2023 at 12:00:30 PM, Sergei Aleksandrovich < ***@***.***> wrote:
I'd recommend checking if the prefix key is redefined in your ~/.tmux.conf
and /etc/tmux.conf configs. Look for something involving C-b or set-option
-g prefix. Also, take note that tmux key bindings are sensitive to
keyboard layout and CapsLock.
—
Reply to this email directly, view it on GitHub
<#165 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATIAWVWTJCMPVOA4T53ZDYHIEK5AVCNFSM6AAAAAA753ZWWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGQ3DINZRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I just recently updated and now Ubuntu 18.04 through WSL2. |
For some odd reason
cntl+b+d
is not terminating a connected rails session anymore. Any advice?The text was updated successfully, but these errors were encountered: