08:01 <balejk> hello, I was wondering whether it would make sense for the spawn-terminal command to make the spawned terminal inherit the current color scheme of the foot instance from which the command was run

09:58 <jpp> what is the Spawn-terminal command? What's it for?

10:17 <balejk> jpp: it runs a new foot instance starting in the same working directory if the shell is correspondingly configured. see foot.ini(5)

13:49 <dnkl> balejk: spawn-terminal doesn't propagate any run-time changes to the new instance, and I don't think we should special case the theme either.

13:50 <balejk> dnkl: the cwd is a run-time change, isn't it?

13:51 <balejk> what about propagating the initial-color-theme setting in some way?

13:52 <balejk> I think I saw an issue open to allow this command to be implemented via an arbitrary command, so if that happened then this would be possible to achieve through that

13:53 <balejk> I meant this issue, but it's about something a bit different actually: https://codeberg.org/dnkl/foot/issues/1856

13:57 <dnkl> balejk: there's another open issue, where foot doesn't propagate the command line options from the original instance. This is something I intend to fix at some point

13:57 <balejk> to elaborate on my use case, simply I use the two themes depending on the surroundinga: during day, I will mostly use the light theme, at night the dark theme. I also often use the Ctrl+Shift+N shortcut to spawn new terminals in the same directory. I have bound a custom command to pass the initial-color-theme value to foot in my window manager, so that all new instances have the right color theme according to the system configuration, that means that I will not b

13:57 <balejk> e blinded by a light theme at night (or vice versa) when I spawn a new terminal. and what I'd like is for that to be the case when launching the terminal in the same cwd via the mentioned command

13:58 <dnkl> we could also consider making it possible to customize the command line executed by spawn terminal

13:58 <balejk> that would be great. propagating the initial-color-theme option wouldn't actually work because the terminal could chnge the theme in the meantime

13:59 <balejk> shall I open a feature request issue for this then?

13:59 <dnkl> https://codeberg.org/dnkl/foot/issues/1622

14:00 <dnkl> for the color theme specifically, wouldn't it be easier to just write (and update) a small config file with initial-window-theme and include that from your main config?

14:01 <dnkl> that way all new instances would get the correct theme regardless of how they're launched

14:02 <balejk> that's actually what I did with the whole theme before the SIGUSR1 switching was implemented. and indeed I think that will be the easiest way to go about this. thanks! :-)

14:04 <dnkl> note that the next release will change the SIGUSR1 semantics somewhat

14:05 <balejk> I see, thanks for the heads up

14:06 <dnkl> https://codeberg.org/dnkl/foot/src/branch/master/CHANGELOG.md#unreleased

14:06 <balejk> yes, I saw it

14:06 <balejk> thank you

14:07 <balejk> and thank you for working on foot, it's great :-)