13:28 <dnkl> sterni: ping, any thoughts on https://codeberg.org/dnkl/foot/issues/569 ?

13:55 <sterni> dnkl: that works as well, I don't think there is a need for you to do anything

13:55 <sterni> dnkl: I'm just unsure if it isn't a bad choice to not install terminfo by default in the future since that may catch users out

13:56 <sterni> I guess it is in generall (for an arch like situation) a good idea to not install it as part of the default package and just depend on the foot-terminfo package

14:04 <dnkl> sterni: I agree that it's probably a bad idea to stop installing it unconditionally. I'll see if we can add an option that disables it, and if possible, allows changing the target directory. But at least allowing you to disable it. That way, distros can use that option instead of manually rm:ing it from the package after building+installing.

15:00 <dnkl> sterni: PR adding -Dterminfo-install-location=disabled|<custom-path> meson option: https://codeberg.org/dnkl/foot/pulls/607

15:15 <sterni> commented.

15:15 <sterni> oh disabled so the build still runs?

15:34 <dnkl> sterni: yeah, but most importantly, to *not* change the default terminfo to 'xterm-256color'

15:37 <sterni> ohhh I see

19:14 <ericonr> hi! is anyone here using foot with IBM Plex font?

19:15 <ericonr> it seems to have issues with emoji which don't appear when using other fonts

19:15 <ericonr> (I'm using latest foot)

19:16 <ericonr> basically they get cut off, and I'd like for that not to happen, since it's my shell prompt :P

19:16 <ericonr> happens with ❯ and ➜

19:16 <dnkl> ericonr: first, have you read https://codeberg.org/dnkl/foot/wiki#user-content-emojis-get-cut-off ?

19:18 <dnkl> ericonr: though in your case, the issue may be that the week around mentioned in https://codeberg.org/dnkl/foot/wiki#user-content-nerd-fonts-powerline-font-awesome-doesn-t-work isn't kicking in

19:18 <dnkl> There's a new option in the master branch that forces all PUA glyphs to be double-width. I suspect that will fix your issue

19:19 <dnkl> And if you don't want to build foot from git, just wait: 1.8 will be released any day now

19:20 <dnkl> s/week around/work around/

19:21 <ericonr> dnkl: https://codeberg.org/dnkl/foot/commit/4c954be7a6d86b21da512fc533eb3362ac737221 ?

19:21 <dnkl> ericonr: that's the one :)

19:23 <ericonr> sad, it doesn't apply cleanly

19:24 <dnkl> Do note that those glyphs *must* be followed by a space to be rendered as double-width.

19:24 <dnkl> (or "nothing", just as long as the next cell is empty)

19:26 <ericonr> it should be #define PROMPT " ➜ "

19:27 <ericonr> dnkl: info output says the setting is applied, but it didn't change anything

19:28 <dnkl> ericonr: ok, I'll have to lookup those codepoints. Perhaps they're not PUA codepoints at all...

19:28 <ericonr> warn: config.c:2123: tweak: PUA double width glyphs enabled

19:28 <ericonr> the issue seems to be font related as well

19:28 <ericonr> doesn't happen on Liberation Sans, for example

19:29 <ericonr> I can try to open a bug (would be nice if it supported oauth with other forges), if you'd like to track it

19:29 <dnkl> We'd have to check which font it's actually loading them from. May not be the primary font at all

19:29 <Arnavion> ( https://unicode-table.com/en/279C/ )

19:30 <dnkl> Arnavion: thanks. So most likely they are defined as single width in the Unicode standard

19:30 <dnkl> But the font glyphs are double width

19:31 <dnkl> Foot tries to detect this, but fails if the glyphs are too small

19:32 <dnkl> I.e wider than a single cell, but but passing foot's threshold for double-width rendering

19:32 <dnkl> ericonr: but yeah, please open a ticket if you'd like to track this. But I'll take a look tomorrow regardless

19:33 <Arnavion> Yes, according to the Rust unicode-width library, ➜ is 1 column wide

19:34 <ericonr> alacritty seems to behave with it

19:34 <dnkl> ericonr: is all else fails, this is what you'd be interested in https://codeberg.org/dnkl/foot/pulls/592

19:35 <dnkl> ericonr: alacritty doesn't clip glyphs to the cell boundary

19:35 <ericonr> ooh

19:35 <ericonr> lol that explains it

19:35 <ericonr> and it's what 592 implements?

19:35 <dnkl> ericonr: it can do that because it always re-renders the entire grid. Foot can't afford that

19:36 <dnkl> Yes, it tries to track glyphs that had overflowed

19:36 <dnkl> Has

19:36 <dnkl> And forces repaints if them when necessary

19:36 <dnkl> Of

19:36 <dnkl> Damn phone