From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
42708@debbugs.gnu.org, rms@gnu.org,
"積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#42708: Let users copy "*Char Help*" buffer
Date: Wed, 11 Nov 2020 13:24:28 -0800 (PST) [thread overview]
Message-ID: <b97e03db-65bb-46ef-8d22-41577137efe0@default> (raw)
In-Reply-To: <87y2j7slmo.fsf@mail.linkov.net>
> > I also wouldn't be happy about wholesale replacement of uses
> > of `read-char-choice' by `read-char-from-minibuffer'.
> > Maybe it makes sense to replace some such occurrences, but
> > it would be good to see some justification case by case.
>
> Actually, only one occurrence of `read-char-choice'
> was replaced by `read-char-from-minibuffer'.
Good.
Could we please know which occurrence you changed,
and what the justification is?
> > But if `read-char-choice' can itself remain in the
> > `read-char', `read-event', `read-key', etc. camp, then at
> > least that will be good, IMO. Thx.
>
> Yes, `read-char-choice' remains in that camp unchanged.
Good. Thanks for that.
next prev parent reply other threads:[~2020-11-11 21:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 13:41 bug#42708: Let users copy "*Char Help*" buffer 積丹尼 Dan Jacobson
2020-08-04 23:42 ` Juri Linkov
2020-08-05 9:24 ` Lars Ingebrigtsen
2020-08-05 23:52 ` Juri Linkov
2020-08-06 7:12 ` Lars Ingebrigtsen
2020-10-13 2:59 ` Lars Ingebrigtsen
2020-10-13 15:27 ` Drew Adams
2020-11-03 18:57 ` Juri Linkov
2020-11-09 13:39 ` Lars Ingebrigtsen
2020-11-10 19:51 ` Juri Linkov
2020-11-10 20:26 ` Drew Adams
2020-11-11 5:40 ` Richard Stallman
2020-11-11 8:09 ` Juri Linkov
2020-11-11 19:41 ` Drew Adams
2020-11-11 20:07 ` Juri Linkov
2020-11-11 21:24 ` Drew Adams [this message]
2020-11-12 7:32 ` Juri Linkov
2020-11-12 18:09 ` Drew Adams
2020-11-11 10:28 ` Lars Ingebrigtsen
2020-11-11 19:19 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b97e03db-65bb-46ef-8d22-41577137efe0@default \
--to=drew.adams@oracle.com \
--cc=42708@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=rms@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.