<dnkl>
that turns it into a no-op. You could use a text-binding instead, to remap it to a plain return.
<dnkl>
or, map the escape sequence emitted by foot to something useful in your shell 😉 (or just map it to the same thing as a plain return)
<anarcat>
how do i "remap it"?
<cbb>
anarcat: adding the following to ~/.inputrc should work, if you're using bash
<cbb>
"\e[27;2;13~": ""
<anarcat>
oh i see
<anarcat>
but that's app-specific
<anarcat>
i'd need to do that in irssi, bash, etc
<cbb>
there's a structural format to the key sequences terminals send
<cbb>
so the ideal solution to this problem would be for apps to start parsing sequences instead of prefix matching them
<cbb>
they'll have no choice if they want to benefit from the modernized kitty keyboard protocol anyway
<anarcat>
lol
<anarcat>
i must be getting old
<cbb>
anarcat: \x0d = Shift+Return
<cbb>
adding that to the [text-bindings] section in foot.ini is what dnkl was referring to
<anarcat>
so wait, is \x0d one of those kitty extensions?
<cbb>
no, \x0d is \r (carriage return)
<cbb>
which is what terminals send for plain Enter in the legacy (not kitty) protocol
<cbb>
what I said about the kitty protocol was a little obscure
<anarcat>
TIL
<cbb>
I meant that if apps start *parsing* key sequences instead of string matching them... they could then easily ignore all sequences they don't recognize
<cbb>
instead of inserting junk into the buffer
<anarcat>
but why does bash interpret \r as ;2;13?
<cbb>
anarcat: How do you mean? When does it do that?
<cbb>
when you press Shift+Enter, foot emits \e[27;2;13~
<cbb>
which bash partially eats and partially inserts, because it's just doing simplistic string matching
<anarcat>
okay so i got this backwards
<anarcat>
text-bindings.\x0d = Shift+Return tells foot to send \r when i hit shift-return?
<cbb>
yes
<anarcat>
okay, so then i guess the question is why foot sends \e[27;2;13~ for shift-return by default :)
<cbb>
to allow you to bind Shift+Return ;)
<cbb>
most terminals emit \r, with or without Shift
<cbb>
which makes Shift+Return impossible to bind
<cbb>
the \e[27...~ thing is an extended key format that xterm calls "modifyOtherKeys"
<cbb>
which some apps recognize and some don't
<cbb>
emitting it by default has some pros and some cons
<cbb>
the most obvious con being that it causes junk to be inserted in apps with primitive key binding support
<anarcat>
gotcha thanks
Biolunar has joined #foot
avane has quit [Remote host closed the connection]
avane has joined #foot
avane has quit [Remote host closed the connection]
avane has joined #foot
bgs has quit [Remote host closed the connection]
ollysmith has quit [Quit: ZNC 1.8.2+deb3+b4 - https://znc.in]