From: "Roméo La Spina" <firstname.lastname@example.org>
To: Ignacio Casso <email@example.com>
Subject: Re: [BUG] Resolving idle clocks needs multiple keystrokes [9.5.2 (release_9.5.2-24-g668205 @ /home/ignacio/repos/emacs/lisp/org/)]
Date: Sun, 20 Mar 2022 22:02:57 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Thanks for your answer! I will do that as soon as I have a little more time.
Ignacio Casso <email@example.com> writes:
>> Hmm, I see the problem. I didn't think about that.
>> Thank you very much for your suggestion. But what about using
>> read-char-exclusive? It seems to have a timeout argument too, and
>> should apparently fix the issue (ie. the prompt will no longer
>> disappear at the first unintentional click).
> That would indeed fix your bug, it seems. Not mine, since it
> does not reset the idle timer either. I suggest you reply
> with a patch, just replacing `read-char' with `read-char-exclusive'.
next prev parent reply other threads:[~2022-03-20 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2022-03-13 20:42 ` Ignacio Casso
2022-03-19 10:07 ` Roméo La Spina
2022-03-19 11:08 ` Ignacio Casso
2022-03-19 12:29 ` Roméo La Spina
2022-03-20 12:21 ` Ignacio Casso
2022-03-20 21:02 ` Roméo La Spina [this message]
2022-03-12 11:07 Ignacio Casso
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).