Is there any way to reload the config file (for dark/light theme switching purposes) or maybe to define sections where we can define dark and light theme variants and send a message to fnott to use the proper section.
Change theme on the fly #38
Currently, no. There's no include statement, no dark/light "modes" and no way to trigger a configuration reload.
If this is something that is wanted, we'd first have to decide on which method to support, and then implement it.
Mako is using makoctl -reload command, waybar is using killall -SIGUSR2 waybar, either of those to reload the configuration file would be fine, I didn't look at fnott implementation, so I have no idea which one would fit best.
Also, as you said, an include statement would be perfect because instead of parsing the file and changing every color, one could just change the include statement.
I have proposed adding a systemd service file. If it were added, then you could do systemctl --user restart fnott:
systemd in turn will be issuing TERM and possibly KILL signals, and then starting fnott again.
The systemd unit would theoretically work but would have the side-effect of killing off any current notifications with it. I would think something like a signal-based reload, or adding a custom fnottctl sub-command to reload the config.
As for setting the color values, I use crudini to directly modify the INI values in the config file.
fnott -reload
Recently created https://github.com/tranzystorekk/catppuccin-fnott, would love to have a less confusing how-to-use guide 😅
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?