03:36 <tkna> When I run `foot tmux`, the color theme is solarized dark theme. Is there any way to disable this?

05:38 <dnkl> tkna: choose a different theme in foot?

05:44 <tkna> dnkl: I do not have a theme or color designation in foot. In other words, we want to be consistent with the original color. If I start only foot in this state, it works as expected, but if I specify tmux as an argument, the color becomes solarized dark.

05:46 <tkna> The same is true if you empty tmux config. When I run `alacritty -e tmux` the colors are as expected.

05:54 <dnkl> tkna: there's always a chilly

05:55 <dnkl> color theme set

05:55 <dnkl> can't tell you why there's a difference with and without tmux, but foot's default color theme from 1.14 is solarized dark

05:56 <dnkl> before that it was zenburn

06:01 <tkna> dnkl Yes, I was using the official package instead of AUR because I could not solve that problem. But with this update, I now have to deal with that situation..

06:28 <dnkl> tkna: the old default colors are included as a theme file. You can simply "include" it in your foot.ini to get the old colors back

06:29 <tkna> dnkl: As for tmux, I think I may have solved the problem, I wanted to disable the foot color specification because I was using this which specifies the color directly to the shell, but I put the `set -g allow-passthrough 1` mentioned here in tmux.conf, and the `foot tmux` now has the expected color! https://github.com/chriskempson/base16-shell

06:32 <tkna> dnkl: However, that does not seem to be possible with respect to the `foot ranger`. Do I really have to explicitly assign a color? Is it possible to disable the color assignment itself?

06:36 <dnkl> tkna: like I said; there's always a predefined set of colors being used. Otherwise the entire window would be white, or black, or transparent (depending on definition of "no color")

06:36 <dnkl> the link you referred to overrides the colors by writing escape sequences to the terminal

06:37 <dnkl> that'll only happen when you're normal shell rc scripts are run, I assume. hence it doesn't work with eg "foot ranger". Nothing foot can do about that

06:42 <tkna> dnkl: Okay, I see what you mean. It looks like I should define the color in foot's config or some other way. Thanks kindly.

06:49 <dnkl> tkna: https://codeberg.org/dnkl/foot/src/branch/master/themes/zenburn

06:49 <dnkl> that's the old default

06:49 <dnkl> it should be packaged with foot, typicall in /usr/share/foot/themes

06:50 <dnkl> all you need to do is "include=<path>" in foot.ini

06:53 <tkna> dnkl: I see. I did change it to `include=/usr/share/foot/themes/zenburn` and it seems to be back to the previous colors. It seems it was the zenburn colors that I thought had been disabled. Understood, thanks. I will use this as the basis for my color specification.

10:22 <dnkl> bapt: btw, thanks for working on the utmp issue! And don't worry, there's no rush :)

10:22 <dnkl> easter holidays now?

10:25 <bapt> no not yet

10:25 <bapt> just too much work to be focus on fixing utmp

10:25 <bapt> :D

10:27 <bapt> but you are right monday will be easter holiday

10:27 <bapt> so nothing before tuesday

10:27 <dnkl> guess I'm lucky then; I have both today and monday off :D

10:28 <dnkl> well, happy holidays, to everyone :)

10:32 <bapt> germany ?

10:33 <bapt> (for once french do work others are off :D, it does not happen that often)

10:34 <dnkl> sweden

10:36 <dnkl> not sure where we are on the "most holidays" scale, but I could certainly use a couple more than what we actually have...

10:37 <bapt> from my searching it seems we are even on the number of bank holidays at least

11:57 <angry_vincent> currently, i set the font to size 8, because 7 is to small. size 8 is also bit too big. when i do ctrl - i getting plausible size. what size is that? 7.5?

11:58 <bapt> yes

11:59 <bapt> angry_vincent: start foot from another foot terminal

11:59 <bapt> you will see what your are searching for in the info printed there

11:59 <angry_vincent> aha, thx!

12:41 <WhyNotHugo> Something that I really liked about foot is that is worked wonderfully out of the box without any tinkering. The new low-contrast theme seems a poor default, since it's now "hard to read" out of the box.

12:41 <WhyNotHugo> Good thing I have alacritty installed so I can reconfigure foot without having to switch to a tty I guess.

12:42 <WhyNotHugo> I guess if you have perfect eyesight that's not an issue.

12:46 <dnkl> WhyNotHugo: there's been lots of complains about the old default as well ;)

12:47 <WhyNotHugo> dnkl: what was wrong with it?

12:47 <dnkl> I guess we could go the boring route and use a generic, high-contrast default. But, solarized is common, and liked by many, so hey, why not

12:47 <dnkl> WhyNotHugo: nothing, and everything 🤷

12:47 <dnkl> some liked it, some hated it. Just like all other color themes

12:48 <WhyNotHugo> grey one green with barely any contrast is a pretty tough combination. I mean, I don't really care THAT MUCH about the colours as long as I can read them easily.

12:48 <WhyNotHugo> Like, as of 0.14, if you install foot you still need another terminal to configure it first (or a tty)? Unless you have top tier eyesight, of course.

12:48 <dnkl> gray? that'd be bright black?

12:49 <WhyNotHugo> I feel it's kinda like defaulting font size to 3px. Sure, some will love it, but those who don't have a hard time changing it.

12:49 <WhyNotHugo> I guess you can't pleast everyone tho XXD

12:49 <dnkl> WhyNotHugo: no, it defaults to 8pt

12:50 <WhyNotHugo> The 3px thing was an analogy.

12:50 <dnkl> ah 😅

12:50 <dnkl> WhyNotHugo: suggestion; start a "competition" to design a new, *unique* color scheme for foot. I.e don't copy anything else

12:51 <dnkl> I agree that the terminal should at least be useable with the defaults

12:51 <dnkl> fwiw, the bright colors in the new default scheme is non-standard (i.e. they're not actually solarized colors). That means I'm open to tweaking them a bit.

12:52 <dnkl> but I kind of like the idea with a foot-custom color scheme as default

12:56 <WhyNotHugo> To like, give foot some "identity" to so call it?

12:57 <dnkl> yeah, in addition to its icon :)

12:57 <dnkl> I'm writing up an issue right now

13:00 <WhyNotHugo> The icon and name definitely have character, rather than being "terminal-xy17" and yet another terminla icon XD

13:00 <WhyNotHugo> Saldy, I think I never see it, since I just launch the terminal via super+return

13:03 <dnkl> same here :|

13:03 <dnkl> :D

13:04 <dnkl> https://codeberg.org/dnkl/foot/issues/1321

13:04 <dnkl> did I miss anything?

13:04 <dnkl> WhyNotHugo: you could also run it as floating, with CSDs... that's a pretty "unique" look 😂

13:13 <rockorager> I ran foot the other day on WSL and wow, seeing those CSDs on a Windows machine was crazy

13:27 <dnkl> rockorager: it's actually pretty cool. Though, last time I tested, Windows didn't handle the CSD's sub-surfaces correctly, and it was a bit glitchy to move the window around, and resize it.

17:39 <kaathewise> dnkl: Posted the issue, but the log doesn'

17:40 <kaathewise> ...'t seem to reveal any issues, at least to me. Would my Sway config be useful?

17:50 <dnkl> kaathewise: there appear to be first a four second delay when loading the fonts (do you have many fonts installed?). But biggest issue seems to be a really long delay after foot has done the initial commit for the main surface, until Sway replies with the first configure event. It *looks* like this is on Sway.

17:51 <dnkl> how is your second monitor connected? To the same graphics card as the first?

17:52 <dnkl> does running "foot -o tweak.max-shm-pool-size-mb=0" help?

18:15 <kaathewise> dnkl: 1. No, only dejavu and jetbrains mono, nothing else

18:15 <kaathewise> dnkl: 2. No idea tbh, I just plugged the HDMI and it worked somehow

18:16 <kaathewise> dnkl: 3. I can't tell the difference visually, it seems to open with the same lag

18:18 <kaathewise> Also I just realized it seems to be working just fine on my external monitor, but not on the laptop one

21:29 <rockorager> dnkl: how do you feel about DECSLRM/DECLRMM?