emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: "Roméo La Spina" <romeo.laspina1@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]
Date: Sun, 09 Oct 2022 11:22:06 +0800	[thread overview]
Message-ID: <87mta5fzq9.fsf@localhost> (raw)
In-Reply-To: <87lex3f7ds.fsf@gmail.com>

Roméo La Spina <romeo.laspina1@gmail.com> writes:

> After some discussion on the subject on another topic (see https://lists.gnu.org/archive/html/emacs-orgmode/2022-03/msg00233.html), I have a small patch that prevents the prompt for disappearing on unwanted events, using `read-char-exclusive'. You will find it enclosed.
> ...
> From 0078523a768f215d8053905f66266cb1d083a7cf Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Rom=C3=A9o=20La=20Spina?= <romeo.la-spina@ens-rennes.fr>
> Date: Mon, 21 Mar 2022 20:00:43 +0100
> Subject: [PATCH] lisp/org-clock.el: Fix bug in prompt for resolving clocks

Thanks! And sorry for the late reply.

The patch looks good, especially since we are using
`read-char-exclusive' in most places already.

Applied onto main with minor amendment to the commit message (I added a
link to this thread).
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=de553d1dc7c587d1f3a853543259f8a14464af54

You are also now listed as a contributor at https://orgmode.org/worg/contributors.html

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2022-10-09  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-22 19:05 Prompt when resolving clocks [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)] Roméo La Spina
2022-03-21 19:03 ` [PATCH] " Roméo La Spina
2022-10-09  3:22   ` Ihor Radchenko [this message]

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=87mta5fzq9.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=romeo.laspina1@gmail.com \
    /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).