New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dunst broke (removed) command line color arguments #34112
Comments
Reverting should be easy, assuming there weren't new features added that people rely on... |
I built 1.6.1 and put the pkg on hold. See some wayland stuff - https://github.com/dunst-project/dunst/blob/master/CHANGELOG.md |
Issue with reverting is that it would mean the package would be kept at an older version forever, I find it hard for upstream to go back in this decision. |
Can't this be defined in dunstrc as
and then called with dunstify -a info "Blabla" "Blabla" -r 1800 |
Upstream closed their issue and this is not a downstream issue. |
they did...sad it's basically left open |
Maybe you could pass the config per command-line like this?
|
doesn't work
|
and now the repo must be updating bc i cant rebuild the old version -.- |
I mean that you write all the command line arguments in config file format like
|
that doesn't look like the example cfg i found, mustve been an old version. thanks ill give it a go! |
Yes, I changed it according to the dunst manual and it works for me with the current version 1.8.1 |
Yep mine is in the same file i had it before. lil ghetto but it works |
System
xuname:
Void 5.15.1 x86_64 AuthenticAMD notuptodate hold rrrmFFFFFFFFFF
package:
dunst-1.7.1_1
Expected behavior
dunst .... -frame_color #123456
changes colors when a notification hitsActual behavior
default colors
Comments
This was upgraded 3 days ago but breaks current functionality. Not sure if there were any reasons for the upgrade but it breaks one-line setups. Functionality may be added back (with 2 dashes instead of 1) but it hasn't happened in 27 days.
Not sure if reverting back to 1.6.1 is an option.
void pr #34074
dunst issue dunst-project/dunst#940
The text was updated successfully, but these errors were encountered: