Replies: 2 comments 1 reply
-
Making a note of tmux commit, the one i am running on Sonoma is |
Beta Was this translation helpful? Give feedback.
1 reply
-
I built on the latest commit |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
no amount of tweaking infocmp to kbs=\177 fixes the issue I'm having where ctrl+h bind gets ignore by tmux.
I have one computer that works fine (M1 Max MBP running Sonoma) and one computer I'm setting up (M4 Mini running Sequoia) that has the problem. I am going to post the relevant config and the relevant tmux server logs from both computers.
tmux config:
Sequoia machine tmux log:
Sonoma machine log:
Yep so the only sense I can make out of comparing these two logs is that on the offending computer we get the unexpected
not found in key table root
. Kind of stuck because I do not know where to look to figure out (aside from possibly infocmpkbs
, and I am starting to feel like that is definitely not relevant) where the mapping is that tmux is supposed to be referencing to convert\b
intoc-h
.I understand that
\b
is supposed to indicate backspace, and that ctrl+h is the traditional backspace ascii character, and I'm fine with ctrl+h being interpreted by my shell as synonymous with backspace but I need to use it for directional left mnemonic functionality in line with h for left in the vim style.I can clearly see that tmux passes the ctrl+h keystroke through to the child pane, which makes it clear that tmux is not doing anything like converting the ctrl+h into a
^?
backspace, because that would cause an inner vim to backspace instead of ctrl+h. The problem here is that even though the C-h bind has been set in tmux config it is not triggering it.infocmp $TERM
from Sequoia machine:infocmp $TERM
from Sonoma machine is identical. I confirmed it, so I don't need to paste it a second time.Beta Was this translation helpful? Give feedback.
All reactions