emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Schumacher <tim@datenknoten.me>
To: emacs-orgmode@gnu.org
Subject: org-show-notification of org-clock.el broken on MS Windows
Date: Fri, 24 Jan 2020 10:08:59 +0100	[thread overview]
Message-ID: <85sgk52pck.wl-tim@datenknoten.me> (raw)

Hi folks,

I have a snippet that clocks me in, if I set the TOOD-keyword of an item to
started. So some time after working on that item on and off, I got a stack trace
and it would not change the keyword to started. The error was, that emacs was
not compiled with dbus support and I thought, hell yeah, I'm on MS Windows, I
don't have dbus here. So I looked at the stack trace and found
org-clock-notify-once-if-expired which wants to show a notification if I took
longer than I estimated. Than digging deeper I found org-show-notification which
is where the actual error happens. It checks if the function
notifications-notify exists and then tries to use it. On my system the function
is available, but does not work because I don't have dbus support.

In my opinion these two actionable items should be done:

* The function org-show-notification should be more robust. It should not fail
  if it can't fire a notification for whatever reason.
* On MS Windows the function w32-notification-notify should be used.

Maybe someone has a quick fix, if not I can try my non existant elisp foo and hack
together a patch tomorrow, but please be gentle with me.

Thanks for your time and great effort into org-mode!

Tim

             reply	other threads:[~2020-01-24  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  9:08 Tim Schumacher [this message]
2020-01-26  8:12 ` org-show-notification of org-clock.el broken on MS Windows Bastien
2020-01-26 11:19   ` Tim Schumacher
2020-01-26 16:37     ` Bastien

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=85sgk52pck.wl-tim@datenknoten.me \
    --to=tim@datenknoten.me \
    --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).