From: SeerLite via Guix-patches via <guix-patches@gnu.org>
To: 59648@debbugs.gnu.org, jonathan.brielmaier@web.de
Subject: [bug#59648] [PATCH] gnu: icedove: Use native notifications when available
Date: Sun, 19 Feb 2023 01:39:51 +0000 [thread overview]
Message-ID: <3fe596c61765c15b1914bd2d2ddc26e5@disroot.org> (raw)
In-Reply-To: <7cc35b95103dd43472eb68b810971060e35aa42b.1669611249.git.seerlite@nixnet.email>
Hi! Sorry, I didn't receive this response when it was sent, and it
wasn't in my inbox.
> Hello SeerNet,
It's SeerLite :s
> hm, when I enable notifications in Thunderbird I get notifications from
> my sway desktop:
> I just enabled it via Settings -> General -> Incoming Messages -> When
> new messages arrive -> [x] Show an alert.
>
> This is without your patch applied...
Yes, that's the same for me as well. The issue is not that there aren't
notifications, but that IceDove chooses to use its own fallback
implementation of them rather than using the program configured to send
them (in my case it's dunst). Without my patch I get large notifications
inconsistent with my setup. With my patch I get my custom configured
dunst notifications.
I'm pretty sure Icecat would use the same fallback notification
implementation if it didn't have libnotify. That's how I found out about
this issue back when I made the patch after all, but I can't remember
the details anymore. All I can say is Icedove uses the right
notifications on my machine with the patch applied.
I hope that explains the difference and maybe you're able to reproduce
the issue.
PS: I was actually actively waiting for a response since I sent the
patch (same as my other patch). Unfortunately I didn't check mumi
earlier. I've also changed my E-mail provider as the server I was
previously using was having a hard time getting to Debbugs.
next prev parent reply other threads:[~2023-02-19 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 4:54 [bug#59648] [PATCH] gnu: icedove: Use native notifications when available SeerLite via Guix-patches via
2022-12-05 16:17 ` Ludovic Courtès
2022-12-08 15:09 ` Jonathan Brielmaier
2023-02-19 1:39 ` SeerLite via Guix-patches via [this message]
2023-04-12 8:34 ` bug#59648: " Jonathan Brielmaier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fe596c61765c15b1914bd2d2ddc26e5@disroot.org \
--to=guix-patches@gnu.org \
--cc=59648@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=seerlite@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).