<dnkl>
I'd assume the foot (and fcft) ebuild require something similar
<Arsen>
interesting
<Arsen>
I can add that dependency
<dnkl>
thanks for looking into it!
<Arsen>
I'll reach out to the maintainer of the package to ask about the cjk useflag and what it does
<Arsen>
I'd expect someone to USE=cjk globally
<Arsen>
so if that breaks programs, that's a problem
<dnkl>
I would guess it's a workaround for some other application, with unforeseen consequences... or the consequences are known and you're just supposed to know about them... 🤷
<dnkl>
anyway, thanks. I'm also interrested in knowing the details of that use flag
<Arsen>
the bug report mentions an API for checking whether a character is ambiguous width
<Arsen>
it might end up being useful to do some general handling there (if there's some other characters that could lead to problems)
<dnkl>
foot can't, by default at least, override a codepoints width, since that will just cause cursor desynchronization unless the TUI/shell is also overriding the width in the same way
<dnkl>
given that, the new API isn't that useful to us. We could perhaps add a config option to foot, where ambi-width codepoints are either forced to 1, 2, or to whatever libutf8proc says
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
<Arsen>
oh, true
* Arsen
murmurs about TUIs not being great
<Arsen>
I've pushed the workaround and emailed the libutf8proc maintainer, I'll get back to you if/when I get a response
<Arsen>
it'll take some time for the workaround to make its way into stable, should you see new reports please ask them to try the testing version of the package
boomboxnation has quit [Read error: Connection reset by peer]