<rockorager>
going back to the handling modifiers: the difficulty is coming because previously, any non-csi sequence produced actual text
<rockorager>
so you could count on that. But if you have kitty flag = 1 and num or caps lock on, you now have to decide if the codepoint + modifiers produce text _in the tui_, as opposed ot being told by the terminal or toolkit
<rockorager>
You have to suddenly special case everything (is it caps lock + a printable key? upper case it and print it, is it num lock too? etc)
<rockorager>
But I guess that's where it's on the TUI to pick the right flags
<rockorager>
And it seems with the logic we are using we shouldn't pick *just* disambiguate...it should be at least disambiguate + report associated text
<rockorager>
"With this flag turned on, all key events that do not generate text ***and some that do*** are represented in one of the following two forms: ..."
<rockorager>
emphasis mine
<rockorager>
words in emphasis mine too
__jmcantrell__ has joined #foot
jmcantrell has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
__jmcantrell__ is now known as jmcantrell
jmcantrell_ has joined #foot
jmcantrell has quit [Client Quit]
jmcantrell_ is now known as jmcantrell
__jmcantrell__ has joined #foot
jmcantrell is now known as Guest7754
Guest7754 has quit [Killed (silver.libera.chat (Nickname regained by services))]
__jmcantrell__ is now known as jmcantrell
jmcantrell_ has joined #foot
<jmcantrell>
i can't seem to get prompt jumping to work in either bash or zsh. i've got the function added to the start of PROMPT_COMMAND in bash and added to the precmd hooks in zsh. ctrl+shift+{z,x} does nothing
<jmcantrell>
i'm testing it in the git version of foot
<jmcantrell>
but it also doesn't work in the latest arch package
<jmcantrell>
nevermind pebkac
jmcantrell has quit [Quit: WeeChat 4.2.1]
h-erectus has joined #foot
h-erectus has quit [Ping timeout: 260 seconds]
hspak has quit [Quit: Ping timeout (120 seconds)]
hspak has joined #foot
<dnkl>
rockorager: I was going to post in the kitty issue, asking him to update the specification to match kitty's implementation. But noticed he'd already done that.
<dnkl>
I've updated foot again
<dnkl>
we should now be back where we started, except for the GTK -> XKB change
<dnkl>
that said, my personal view is that disambiguate only isn't something a new/modern application would use. To me, that's more lika a hack to an already existing application, that perhaps does simple pattern-based key matching instead of VT parsing it
<dnkl>
at least that's the conslusion I reached when implementing my own kitty-enabled TUI application :)
narodnik has quit [Quit: WeeChat 4.2.1]
narodnik has joined #foot
rrogalski has quit [Quit: Quit: Dog probably tripped over power cord again.]
rrogalski has joined #foot
baltazar has quit [Ping timeout: 256 seconds]
baltazar has joined #foot
SusanTheNerd has quit [Remote host closed the connection]
SusanTheNerd has joined #foot
SusanTheNerd has quit [Remote host closed the connection]
SusanTheNerd has joined #foot
SusanTheNerd has quit [Remote host closed the connection]
SusanTheNerd has joined #foot
boomboxnation has quit [Remote host closed the connection]