Skip to content

Commit f830693

Browse files
Add Dunst usage info (#60)
1 parent 64a9838 commit f830693

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

USAGE.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ For more general usage, look at the [Usage section] in [README.md].
1515
- [fzf](#fzf)
1616
- [bat](#bat)
1717
- [qutebrowser](#qutebrowser)
18+
- [rofi](#rofi)
19+
- [dunst](#dunst)
1820

1921
## Shell completions
2022

@@ -477,6 +479,27 @@ hook = "cp -f %f ~/.config/rofi/base16-theme.rasi"
477479
@theme "~/.config/rofi/base16-theme.rasi"
478480
```
479481

482+
## Dunst
483+
Add the following to `~/.config/tinted-theming/tinty/config.toml`:
484+
485+
```toml
486+
[[items]]
487+
path = "https://github.com/tinted-theming/base16-dunst"
488+
name = "base16-dunst"
489+
themes-dir = "themes"
490+
hook = "cp -f %f ~/.config/dunst/dunstrc && systemctl --user restart dunst"
491+
```
492+
493+
The above `hook` assumes `dunst` is being managed as a service. If that is not the case, you will need to handle the restart for your system accordingly.
494+
495+
The above workflow is an all or nothing ordeal as the `dunstrc` configuration file does not appear to support importing or including additional files.
496+
497+
However, limited testing has shown `dunst` will not complain if its configuration file contains multiple `[global]` sections. This means we can persist our tinty-agnostic settings (fonts, etc) in a separate file and then use our `hook` to concatenate them like so:
498+
499+
```toml
500+
hook = "cat ~/.config/dunst/dunstrc.local %f > ~/.config/dunst/dunstrc && systemctl --user restart dunst"
501+
```
502+
480503
[Usage section]: https://github.com/tinted-theming/tinty?tab=readme-ov-file#usage
481504
[README.md]: https://github.com/tinted-theming/tinty/blob/main/README.md
482505
[bat]: https://github.com/sharkdp/bat

0 commit comments

Comments
 (0)