06:45 <dnkl> lechner: across multiple screens? The obvious one; the screens are at different viewing distance - font will have the same size, but appears not to.

06:45 <dnkl> another possibility: you're using a bitmap font

06:46 <dnkl> third possibility: one of your screens is lying about its DPI

07:24 <dnkl> fourth possibility: rounding may cause a 1px difference, depending on your configured font size, and the exact DPI values of the monitors

08:25 <florhizome[m]> What's the possible downside of building foot without terminfo?

08:31 <dnkl> florhizome[m]: well, you *need* a valid terminfo. So, if you're not building foot's own, and you don't have an ncurses version with a "foot" terminfo, then you *must* set another terminfo for foot. For example, xterm-256color

08:32 <dnkl> the main downside of that is if ncurses, in the future, adds definitions, or changes definitions, to something that isn't supported in foot. Then applications will start failing in weird ways

08:32 <dnkl> if you'

08:32 <dnkl> if you're a tmux user, you may also be interrested in https://codeberg.org/dnkl/foot/wiki#user-content-foot-s-terminfo-vs-ncurses-terminfo

08:39 <florhizome[m]> We are talking about the meson option?

08:42 <sochotnicky> fwiw, the option just turns on/off generation of the terminfo right? It does not impact foot binary in any way?

08:43 <florhizome[m]> That would be the question, yes. I saw manjaro is doing that.

08:43 <dnkl> ah, right. No, it does not have any effect on the binary itself

08:43 <dnkl> florhizome[m]: https://codeberg.org/dnkl/foot/src/branch/master/INSTALL.md#user-content-setup

08:45 <dnkl> it's fairly common in distro builds, I think .They usually package the terminfo in a separate package, and it often makes sense to build/install the terminfo manually

12:06 <lechner> dnkl: thanks! how can i get the physical size (or dpi) reported by my monitors, please? http://paste.debian.net/1237830/

12:09 <dnkl> lechner: you can look at foot's log output

12:10 <dnkl> post the log output (all of it) when you move a window between two monitors, and I'll have a look

12:13 <lechner> dnkl: i am not sure where to find your log, but i have a problem with the first monitor here. the font ends up being too small http://paste.debian.net/1237834/

12:14 <dnkl> just run foot from another terminal

12:16 <dnkl> those three last monitors the same brand/model? looks weird that all the have exactly the same DPI

12:16 <dnkl> first one, is that a 40" TV?

12:17 <lechner> yes

12:17 <lechner> the other two are indeed the same

12:17 <lechner> here is the move with dpi-aware=yes http://paste.debian.net/1237835/

12:18 <lechner> viewing distance is identical

12:19 <lechner> i think i figured out why foot is so fast: using 8 rendering threads

12:25 <dnkl> math looks right to me, assuming the info is correct (40", 1360x768)

12:26 <dnkl> thing with TVs is that people often _say_ they're at the same viewing distance, but they're not _really_. So, one can always take a (physical) ruler, and check the font size.

12:29 <dnkl> it's also quite possible the screen isn't actually 40"

12:30 <dnkl> try entering your TV's specs here: https://www.calculators.tech/dpi-calculator?, then check if your TV's panel size matches the horizontal/vertical sizes you get there

12:33 <lechner> the tv is in front of me at the same distance. should the result be tha same for dpi-aware=yes and =no? is the main config section okay for it?

12:35 <dnkl> dpi-aware goes into the main config, yes. Foot would have given you an error message otherwise

12:36 <dnkl> I would expect a different font size with dpi-aware=no. For your regular monitors, the difference will be minimal, since their DPI is so close to 96. But there should definitely be a difference on the tv

12:37 <dnkl> (dpi-aware _is_ being applied - we can see that in your log output, when the font is getting reloaded. It's using the monitor's DPI, and not the default 96)

12:38 <dnkl> I hooked up my own 40" TV, just to see if anything funny is going on. Unfortunately, my TV thinks its 7"...

12:38 <lechner> is there a good site to post a screen shot?

12:40 <dnkl> screenshot isn't really going to help here. We already see the font loaded is small (it's 5px). But that's to be expected with a DPI that low

12:40 <dnkl> but https://0x0.st/ can do images, I think

12:42 <dnkl> btw, that's a *really* old build of foot... (not that I think that matters here)

12:49 <dnkl> lechner: what model is the TV?

12:59 <lechner> Samsung LN332A330JID rev C

13:17 <dnkl> lechner: everythin I can find on that model says it's 32", not 40"

13:18 <lechner> you are right

13:18 <lechner> they must have measured the frame

13:20 <dnkl> not much we can do when the metrics aren't correct... :/

13:22 <Lord> Samsung monitors's name contain their size

13:22 <Lord> Ln3 32" …

13:25 <lechner> i am not sure foot can read the label