Please add suport for Dunst

[Minda1975]

Hello. Thank you for your hard work with this project. I have one request. Would it be possible to extend the functionality of the program by adding dunst (it is a lightweight replacement for the notification-daemons provided by most desktop environments) support?

[ltgouvea]

You can customize and use this little script to reload dunst with wal colors with -o reload_dunst.sh (if I remember correctly I've dug this out of some old commits on this repository)

#!/usr/bin/env bash
#
# Script to set colors generated by 'wal'
# https://github.com/dylanaraps/wal
 # Source generated colors.
. "${HOME}/.cache/wal/colors.sh"

 reload_dunst() {
    pkill dunst
    dunst \
	-frame_width 0 \
        -lb "${color0}" \
        -nb "${color0}" \
        -cb "${color0}" \
        -lf "${color7}" \
        -bf "${color7}" \
        -cf "${color7}" \
        -nf "${color7}" &
}

reload_dunst

[Minda1975]

You can customize and use this little script to reload dunst with wal colors with -o reload_dunst.sh

Hello. It works partly. In urgency_low, theme changed, but in urgency_normal, not. Here screenshot. I'm hoping this will help

[ltgouvea]

You can customize and use this little script to reload dunst with wal colors with -o reload_dunst.sh

Hello. It works partly. In urgency_low, theme changed, but in urgency_normal, not. Here screenshot. I'm hoping this will help

Hmm, I can't reproduce this error, the script is working for me. I'm using Dunst version 1.3.0 (2018-01-05)

[Minda1975]

I'm using Dunst version 1.3.0 (2018-01-05)

I'm using Dunst version 1.1.0 (i am on Debian 9.5)...Maybe you could give advice on this? If not, it does not matter. It should be as it is 😄

[ltgouvea]

It seems Dunst has deprecated such flags (dunst-project/dunst#328) BUT here's the funny thing: Deprecation seems to have happened in version 1.2.0 according to their changelog, I'm using a later version and it's working, you're using one pre-deprecation and getting this weird behaviour.....

[Minda1975]

It seems Dunst has deprecated such flags

It does not matter anymore. I made the configuration manually. Thank you for the help.

[Minda1975]

I will close this issue.

[donovanglover]

If anyone else is interested, I solved this issue by writing my dunstrc as a user template file and symlinking the resulting cache file to ~/.config/dunst/dunstrc.

[Minda1975]

I solved this issue

Thank you for this idea. In the near future I will try.

[Minda1975]

If anyone else is interested, I solved this issue by

Thank you, GloverDonovan, very much for this tip. Now dunst working the way I wanted.

[Minda1975]

Finally, with a calm heart😊💗, I can close this problem. Good luck.

[amenpunk]

If anyone else is interested, I solved this issue by writing my dunstrc as a user template file and symlinking the resulting cache file to ~/.config/dunst/dunstrc.

ohhh ty! <3

[Rockenstien]

If anyone else is interested, I solved this issue by writing my dunstrc as a user template file and symlinking the resulting cache file to ~/.config/dunst/dunstrc.

I am getting this error, I have done symlinking but still getting this error
WARNING: Invalid color string: '{foreground}'
WARNING: Invalid color string: '{background}'
WARNING: Invalid color string: '{color4}'
WARNING: Invalid color string: '{foreground}'
WARNING: Invalid color string: '{background}'
WARNING: Invalid color string: '{color4}'

[masonj5n]

I know this is a year later, but @Rockenstien, you need to create the symlink to the generated file in ~/.cache/wal/dunstrc, not the dunstrc file in ~/.config/wal/templates/dunstrc. You have to run pywal at least once to get that file generated from the template.