08:18 <ninewise> dnkl, seem like I'm on the latest version of foot

08:18 <ninewise> I've found a workaround with `TERM=st ncspot` though, and things seem compatible enough

08:22 <dnkl> ninewise: it's not the foot version, but ncurses

08:22 <dnkl> assuming you use the default TERM

08:24 <ninewise> I did before that workaround, yes. My ncurses version is 6.4, I'll have a look at their releases

08:24 <ninewise> looks like that's the latest as well

08:27 <dnkl> ninewise: run "infocmp -x | grep kxOUT"

08:28 <dnkl> if you have a match, your terminfo is good

08:28 <dnkl> and if so, the issue is in ncspot

08:28 <ninewise> I have a match

08:28 <ninewise> Sadness. I'll go and have a look there.

08:28 <ninewise> Thanks for the help!

08:29 <dnkl> my guess would be that it uses the XM capability

08:29 <dnkl> it enables the focus events

08:29 <dnkl> (among other things)

08:31 <ninewise> Oh interesting, they allow compiling with different curses backends by just changing an option...

20:53 <psusi> so I'm reading an article on grapheme clusters, and it shows two versions of a grapheme, one with the zero with joiner, and one without. It's 🧑‍🌾 and 🧑🌾. Firefox seems to treat the former as a single character, but emacs and foot seem to treat them both as one... at least foot here on my older debian system.

20:53 <psusi> err, sorry, I meant to say emacs and foot treat them both as two characters

20:53 <psusi> is this what changed? new versions of foot properly treat this as one character?

20:53 <psusi> but emacs doesn't, so the two don't agree?

20:56 <psusi> how the hell have we come to the point that 32 bits isn't enough to represent all characters? heh.

20:57 <psusi> 4 BILLION... how can there be more characters than that?

21:01 <psusi> ohh, it seems someone has come up with a way for the program to negotiate with the terminal whether to use proper grapheme support, or stick to using wcwidth(). https://mitchellh.com/writing/grapheme-clusters-in-terminals

21:01 <psusi> maybe foot needs to implement this?

21:02 <psusi> ohh, it says that foot does... hrm...

21:03 <psusi> also bash treats that as two characters here on my older version of foot in debian

21:11 <rockorager> psusi: you probably need a newer version of foot

21:11 <rockorager> I think it needs to be compiled with harfbuzz too

21:12 <rjarry> rockorager: in order to support fonts with embedded WASM code ? lol

21:22 <psusi> I have the new one on my gentoo machine and that's where the terminal gets all fubar

21:23 <psusi> I bisected it back to where this change was made to not use wcslen

21:25 <psusi> when I look at it using putty from windows, it looks like a little credit card icon. When I look at it on my gentoo machine in foot, it shows as two blocks.

21:26 <psusi> emacs describe-char says it is unicode point 9000

21:27 <psusi> how can I try typing that in foot? I thought it was ctrl-shift-u to type unicode points?

21:27 <psusi> but that doesn't seem to work in foot

21:30 <psusi> ⌨

21:30 <psusi> I think I manged to type that correctly in emacs with C-x 8 ret

21:32 <psusi> hrm.. but when I paste that into foot it thinks it's just a single width character

21:35 <psusi> hrm... when I open it in my local gui emacs it shows two characters. describe-char says the first is hex 2328 and the second is variation selector 16

21:36 <psusi> what the hell is "variation selector"?

21:37 <rockorager> you don’t want to know

21:37 <psusi> emacs in the terminal thinks it is only one character and does not show the variation selector

21:38 <psusi> ugh... I hate unicode.

21:38 <psusi> I just want to go back to ASCII

21:38 <rockorager> you probably want to set 'grapheme-width-method=wcswidth'

21:38 <rockorager> in foot.ini

21:38 <psusi> I'm still not over the whole pipe vs bar vs broken bar thing.

21:44 <psusi> I still have a keyboard at work that shows | with a whole in the middle. But most of my coworker's keyboards don't have the whole. Neither does this one at home apparently.

21:44 <psusi> s/whole/hole

21:45 <psusi> it always had a hole in DOS... how did I not get the memo that this was changed until like two months ago?