From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: desktop notifications (Re: idea for capture anywhere in x)
Date: Wed, 26 Oct 2022 14:41:42 +0700 [thread overview]
Message-ID: <tjaobn$qoe$1@ciao.gmane.io> (raw)
In-Reply-To: <CAJcAo8u40XArcZMJbNc_ovboO1uSzq2Cf2qCePB36ASOG_QTTA@mail.gmail.com>
On 26/10/2022 13:22, Samuel Wales wrote:
> i have the daemon and the binary but notify-send "summary" "text"
> seems to do nothing obvious. called from shell mode. my emacs is
> maximized. so is firefox.
Does notify-send complain (with some delay) concerning timeout during
attempt to connect to d-bus?
I have found an Eric's message recommending dunst as a notification
daemon for fluxbox.
Firefox has a fallback implementation to display notifications in the
case of d-bus failure, so it is not the best app to test their appearance.
Fluxbox released versions (e.g. from Debian and Ubuntu packages) has a
bug that may cause some applications, in particular Firefox, to be
displayed above other windows. So it may hide a notification window.
However if you have a terminal application in front of you, it should
not be your case.
I am unsure if functions from notifications.el are better than
notify-send in respect to error reporting.
Have you considered playing a tune as a notification?
next prev parent reply other threads:[~2022-10-26 7:45 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 4:22 idea for capture anywhere in x Samuel Wales
2020-09-08 5:01 ` Tim Cross
2020-09-08 5:05 ` Samuel Wales
2020-09-08 5:21 ` Tim Cross
2020-09-08 7:18 ` Maxim Nikulin
2020-09-08 8:03 ` Diego Zamboni
2020-09-08 16:08 ` Maxim Nikulin
2020-09-08 5:39 ` Maxim Nikulin
2020-09-08 22:40 ` Samuel Wales
2020-09-09 4:52 ` Maxim Nikulin
2020-09-10 14:23 ` Maxim Nikulin
2020-09-12 8:48 ` Nick Econopouly
2022-06-10 2:35 ` Samuel Wales
2022-06-10 9:59 ` Charles Philip Chan
2022-06-11 4:11 ` Ihor Radchenko
2022-06-13 7:46 ` Max Nikulin
2022-06-13 9:10 ` Michal Politowski
2022-06-13 10:04 ` Max Nikulin
2022-06-13 14:02 ` Michal Politowski
2022-10-12 1:09 ` Samuel Wales
2022-10-09 14:47 ` Jean Louis
2022-10-09 16:40 ` Max Nikulin
2022-10-09 17:08 ` Jean Louis
2022-10-10 17:16 ` Max Nikulin
2022-10-10 22:06 ` Jean Louis
2022-10-11 9:11 ` Juan Manuel Macías
2022-10-12 1:09 ` Samuel Wales
2022-10-15 3:40 ` Max Nikulin
2022-10-26 4:40 ` Samuel Wales
2022-10-26 4:58 ` Ihor Radchenko
2022-10-26 5:05 ` Samuel Wales
2022-10-26 6:05 ` desktop notifications (Re: idea for capture anywhere in x) Max Nikulin
2022-10-26 6:22 ` Samuel Wales
2022-10-26 7:41 ` Max Nikulin [this message]
2022-10-26 8:07 ` Samuel Wales
2022-10-26 8:29 ` Max Nikulin
2022-10-27 6:33 ` Getting X selection reliably " Max Nikulin
2022-10-28 4:59 ` Samuel Wales
2022-10-28 5:16 ` Max Nikulin
2022-10-28 8:39 ` Dr. Arne Babenhauserheide
2022-10-28 16:38 ` Max Nikulin
2022-10-28 23:07 ` Samuel Wales
2022-10-29 3:21 ` Max Nikulin
2022-10-29 2:59 ` Ihor Radchenko
2022-10-29 3:30 ` Max Nikulin
2022-10-29 6:03 ` Samuel Wales
2022-10-29 7:33 ` Max Nikulin
2022-10-29 22:33 ` Samuel Wales
2022-10-29 4:50 ` Samuel Wales
2022-10-29 4:59 ` Ihor Radchenko
2022-10-29 7:44 ` desktop notifications " Max Nikulin
2022-10-29 23:07 ` Samuel Wales
2022-10-30 4:49 ` Ihor Radchenko
2022-11-13 4:54 ` Getting X selection reliably " Ihor Radchenko
2022-11-13 11:03 ` Max Nikulin
2022-11-14 2:06 ` Ihor Radchenko
2022-11-16 4:03 ` Samuel Wales
2022-11-16 16:46 ` Debugging firefox extension " Max Nikulin
2022-11-17 3:16 ` Samuel Wales
2022-11-17 9:42 ` Jean Louis
2022-11-17 16:12 ` Max Nikulin
2022-11-17 7:18 ` Getting X selection reliably " Jean Louis
2022-11-17 15:30 ` Reliability of org-protocol browser extensions Max Nikulin
2022-12-04 5:21 ` Getting X selection reliably (Re: idea for capture anywhere in x) Max Nikulin
2022-10-12 17:16 ` idea for capture anywhere in x Max Nikulin
2022-10-12 20:06 ` Jean Louis
2020-09-09 8:40 ` Russell Adams
2020-09-09 21:11 ` Samuel Wales
2020-09-09 1:07 ` Ihor Radchenko
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='tjaobn$qoe$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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/emacs/org-mode.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).