sefidel has quit [Remote host closed the connection]
sefidel has joined #foot
narodnik has joined #foot
vyryls has joined #foot
Biolunar has quit [Quit: brb]
<jmcantrell>
anyone here use foot with tmux and are able to view sixel images? foot without tmux works here, but i'm just trying to rule out foot as the culprit
Biolunar has joined #foot
Biolunar has quit [Client Quit]
Biolunar has joined #foot
<bookworm>
tmux has sixel now?
<bookworm>
heh, least on Arch the thing is still in the testing repo that has the option enabled. Might be that
<bookworm>
funnily it's just the line editing though.. .the output of the echo is fine
<bookworm>
is that a zsh thing then?
<dnkl>
yes
<bookworm>
fun
<dnkl>
very few terminal applications support ZWJ emojis properly
<bookworm>
I get it for ncurses... but why the input line is screwed is something I don't understand
<bookworm>
I though that was handled by the kernel?
<dnkl>
zsh handles its prompt, not the kernel. other shells behave differently
<bookworm>
I see
<dnkl>
if you want to test the kernels handling, run "cat -"
<bookworm>
ah, cool
<bookworm>
indeed there it works
<sgm>
huh, interesting
<sgm>
I suppose we are doomed and prone to this kind of attacks, then ;-)
<bookworm>
no but the fix is non trivial... the whole grid kinda wants you to do chars... combining things (including ligatures, non latin scripts etc) are a bit of a mess if you get to the specifics. Moving one cell to the right suddenly doesn't just move the char pointer by one but by a whole grapheme (cluster? unsure about the terminology)
<sgm>
when I've pasted this kind of emoji to eg. sublime text, then hit backspace, it resolves this emoji into two separate characters, then hit backspace again three times to remove the last character, then two times to remove first character, so... it's a lot of crap there
<sgm>
as I'm reading people don't want to implement this because of performance implications, to be the first reason
<sgm>
In emails I don't get any of this crap, ie. no one is sending ZWJ emojis, yet. But when this becomes more and more of a "standard", then I probably should somehow disable this globally..
<sgm>
nevertheless, my Saturday is not worth any more time to spend on this :-) thanks for help!~