From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] dunst broke (removed) command line color arguments
Date: Wed, 17 Nov 2021 14:38:59 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34112@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
New issue by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/34112
Description:
### 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 https://github.com/void-linux/void-packages/pull/34074
dunst issue https://github.com/dunst-project/dunst/issues/940
next reply other threads:[~2021-11-17 13:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 13:38 zlice [this message]
2021-11-17 15:22 ` ericonr
2021-11-17 15:28 ` ct0br0
2021-11-17 15:28 ` ct0br0
2021-11-17 15:29 ` zlice
2021-11-17 19:16 ` ericonr
2021-11-18 9:15 ` biopsin
2022-03-08 20:22 ` tibequadorian
2022-03-08 21:36 ` [ISSUE] [CLOSED] " zlice
2022-03-08 21:36 ` zlice
2022-03-08 21:42 ` tibequadorian
2022-03-08 22:08 ` zlice
2022-03-08 22:14 ` zlice
2022-03-08 22:20 ` tibequadorian
2022-03-08 22:25 ` zlice
2022-03-09 12:49 ` tibequadorian
2022-03-09 13:29 ` zlice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34112@inbox.vuxu.org \
--to=zlice@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).