h-erectus has quit [Remote host closed the connection]
h-erectus has joined #foot
h-erectus has quit [Remote host closed the connection]
h-erectus has joined #foot
h-erectus has quit [Ping timeout: 260 seconds]
h-erectus has joined #foot
h-erectus has quit [Quit: h-erectus]
erectus has quit [Ping timeout: 260 seconds]
erectus has joined #foot
erectus has quit [Ping timeout: 260 seconds]
erectus has joined #foot
alexherbo2 has joined #foot
chiselfuse has quit [Ping timeout: 260 seconds]
sgm has quit [Ping timeout: 260 seconds]
alexherbo2 has quit [Remote host closed the connection]
chiselfuse has joined #foot
sgm has joined #foot
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
chiselfuse has quit [Read error: Connection reset by peer]
chiselfuse has joined #foot
lbia has joined #foot
sgm has quit [Remote host closed the connection]
sgm has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
sgm has quit [Remote host closed the connection]
sgm has joined #foot
<rockorager>
dnkl: here's a fun one
<rockorager>
kitty keyboard with disambiguate flag. Shift+space is encoded as \x1b[32;2u
<rockorager>
shift+space actually generates text though, so per the spec it should be encoded as the utf8 text ' '
<rockorager>
I found the issue but not entirely sure on the best fix
<rockorager>
Issue is that xkb doesn't report the shift modifier as consumed
<rockorager>
And without that consumed, we don't enter the logic to encode it as straight utf8
<rockorager>
From xkb docs: A single modifier is considered consumed if the keysyms produced for the key when it is the only active modifier are different from the keysyms produced when no modifiers are active.
<rockorager>
but space and shift+space generate the same keysym
<rockorager>
right now the code just checks if the effective mods modulo caps_num = 0, but I think it should also print utf8 text if the codepoint was printable and shift was the only mod
<rockorager>
at least that's my best guess currently
<dnkl>
we can't special case shift. Just because we *think* it behaves in a certain way doesn't mean it does in all keymaps
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
narodnik has quit [Quit: WeeChat 4.2.1]
<dnkl>
the shift consumed issue has popped up before. For example, backspace often had the same issue. That can cause issues with foot's own key bindings.
<dnkl>
I've always thought of them as keymap bugs...
narodnik has joined #foot
narodnik has quit [Quit: WeeChat 4.2.1]
alexherbo2 has quit [Remote host closed the connection]
<rockorager>
Why check for mods at all? Does xkb report text for modified keypresses sometimes?
<rockorager>
In other words, if there is utf8 can we correctly assume text was generated?
narodnik has joined #foot
narodnik has quit [Quit: WeeChat 4.2.1]
narodnik has joined #foot
<dnkl>
don't remember... we could test a few combinations, and see what xkb reports
<jpp>
hi
<jpp>
I get an error message when I run tmux on the foot terminal
<jpp>
missing or unsuitable terminal: foot
<j`ey>
jpp: sounds like missing terminfo maybe
<jpp>
Please note that I am connected to ssh when I run tmux.
<j`ey>
try: TERM=xterm-256color tmux
lack has quit [Ping timeout: 272 seconds]
<jpp>
Sorry, I don't speak English. I use DeepL to translate.
<jpp>
Isn't there someone who speaks French here who could help me?
<j`ey>
essayer: TERM=xterm-256color tmux
<jpp>
C'est-à-dire ?
<jpp>
C'est quoi "TERM=xterm-256color tmux" ?
<j`ey>
a la terminal
<jpp>
Le terminal il s'appelle comment ?
<jpp>
xterm ?
<j`ey>
le pied peut faire semblant d'être xterm
<jpp>
ok
<jpp>
Comment ?
<j`ey>
TERM=xterm-256color tmux
<jpp>
Dans quoi ?
<j`ey>
ssh
<jpp>
Quand je tape la commande ssh....... Je rajoute la suite TERM=xterm-256color tmux ?
<j`ey>
yes, instead of just tmux, type TERM=xterm-256color tmux