From: "Roméo La Spina" <email@example.com>
Subject: Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]
Date: Tue, 22 Feb 2022 20:05:34 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
Your bug report will be posted to the Org mailing list.
I have a little problem concerning org-clock.
When resolving clocks, either because of a long idleness or because of
dangling clocks, there is a prompt to ask the user if they want to keep
idle time, substract it, etc...
But when another event than the response occurs (typically, I come back
to my computer, I don't see the prompt and I click somewhere), an
exception "Non-character input event" is raised, and the prompt
disappear, making it impossible to resolve the clock later.
When googling the error message I saw that the problem might be due to
the use of the function read-char when prompting the user, which is
indeed used in the function that resolve clocks.
Is there a solution to wait for the user to answer the prompt, like a
classical yes-no prompt?
Emacs : GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.27, cairo version 1.17.4)
Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)
next reply other threads:[~2022-02-22 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 19:05 Roméo La Spina [this message]
2022-03-21 19:03 ` [PATCH] " Roméo La Spina
-- strict thread matches above, loose matches on Subject: below --
2022-02-22 19:05 Roméo La Spina
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).