Change theme on the fly #38

Open
opened 5 months ago by flipflop133 · 3 comments

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.

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.
Owner

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.

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.
dnkl added the
enhancement
label 5 months ago
Poster

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.

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:

#48

systemd in turn will be issuing TERM and possibly KILL signals, and then starting fnott again.

I have proposed adding a systemd service file. If it were added, then you could do `systemctl --user restart fnott`: https://codeberg.org/dnkl/fnott/pulls/48 systemd in turn will be issuing TERM and possibly KILL signals, and then starting `fnott` again.
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.