Skip to content
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

Closed
zlice opened this issue Nov 17, 2021 · 13 comments
Closed

dunst broke (removed) command line color arguments #34112

zlice opened this issue Nov 17, 2021 · 13 comments

Comments

@zlice
Copy link
Contributor

zlice commented Nov 17, 2021

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 hits

Actual 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

@ericonr
Copy link
Member

ericonr commented Nov 17, 2021

Reverting should be easy, assuming there weren't new features added that people rely on...

@zlice
Copy link
Contributor Author

zlice commented Nov 17, 2021

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

@ericonr
Copy link
Member

ericonr commented Nov 17, 2021

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.

@biopsin
Copy link
Contributor

biopsin commented Nov 18, 2021

Can't this be defined in dunstrc as

[test]
	appname = "info"
	background = "#9dbc8e"
	foreground = "#ffffff"

and then called with dunstify -a info "Blabla" "Blabla" -r 1800

@tibequadorian
Copy link
Contributor

Upstream closed their issue and this is not a downstream issue.

@zlice
Copy link
Contributor Author

zlice commented Mar 8, 2022

they did...sad it's basically left open

@zlice zlice closed this as completed Mar 8, 2022
@tibequadorian
Copy link
Contributor

Maybe you could pass the config per command-line like this?

dunst -conf - <<EOF
... (config options here) ...
EOF

@zlice
Copy link
Contributor Author

zlice commented Mar 8, 2022

doesn't work

dunst -mouse_left_click do_action -mouse_middle_click close_all -mouse_right_click close_current -notification_height 40 -history_len 5 -confg - <<EOF
  [global]
    icon_position = off
  [frame]
    color = "#ff0000"
EOF

@zlice
Copy link
Contributor Author

zlice commented Mar 8, 2022

and now the repo must be updating bc i cant rebuild the old version -.-

@tibequadorian
Copy link
Contributor

I mean that you write all the command line arguments in config file format like

dunst -conf - <<EOF
  [global]
    icon_position = off
    mouse_left_click = do_action
    mouse_middle_click = close_all
    mouse_right_click = close_current
    height = 40
    history_length = 5
    frame_color = "#ff0000"
EOF

@zlice
Copy link
Contributor Author

zlice commented Mar 8, 2022

that doesn't look like the example cfg i found, mustve been an old version. thanks ill give it a go!

@tibequadorian
Copy link
Contributor

Yes, I changed it according to the dunst manual and it works for me with the current version 1.8.1

@zlice
Copy link
Contributor Author

zlice commented Mar 9, 2022

Yep mine is in the same file i had it before. lil ghetto but it works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants