From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@catern.com>
Cc: sbaugh@janestreet.com, 64425@debbugs.gnu.org
Subject: bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help
Date: Mon, 03 Jul 2023 16:28:12 +0300 [thread overview]
Message-ID: <83o7ktm8er.fsf@gnu.org> (raw)
In-Reply-To: <4beb74b6-6bbc-4e0f-9b95-f95b7edf79b9@email.android.com> (message from Spencer Baugh on Mon, 03 Jul 2023 13:19:27 +0000 (UTC))
> Date: Mon, 03 Jul 2023 13:19:27 +0000 (UTC)
> From: Spencer Baugh <sbaugh@catern.com>
> Cc: Spencer Baugh <sbaugh@janestreet.com>, 64425@debbugs.gnu.org
>
> > diff --git a/doc/emacs/mini.texi b/doc/emacs/mini.texi
> > index 9bf4da67644..517a6262522 100644
> > --- a/doc/emacs/mini.texi
> > +++ b/doc/emacs/mini.texi
> > @@ -393,7 +393,7 @@ Completion Commands
> > @vindex minibuffer-completion-auto-choose
> > @item M-@key{DOWN}
> > @itemx M-@key{UP}
> > -While in the minibuffer, these keys navigate through the completions
> > +These keys navigate through the completions
>
> I don't understand this change: do you mean that these keys are
> available not only in the minibuffer?
>
> Yes, my change adds bindings for them also in the completions buffer. So they can be used identically
> in both places.
Then the manual should say "in the minibuffer and in the completions
buffer".
next parent reply other threads:[~2023-07-03 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4beb74b6-6bbc-4e0f-9b95-f95b7edf79b9@email.android.com>
2023-07-03 13:28 ` Eli Zaretskii [this message]
2023-07-03 13:31 ` bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help Spencer Baugh
2023-07-03 13:43 ` Eli Zaretskii
2023-07-03 14:00 ` Spencer Baugh
2023-07-06 7:43 ` Eli Zaretskii
2023-07-06 13:00 ` Spencer Baugh
2023-07-08 9:53 ` Eli Zaretskii
[not found] <e7933bfa-c6e1-4586-b9f0-8bc3555329ef@email.android.com>
2023-07-08 13:51 ` Eli Zaretskii
2023-07-02 16:31 sbaugh
2023-07-02 17:16 ` Eli Zaretskii
2023-07-02 19:14 ` sbaugh
2023-07-03 11:21 ` Eli Zaretskii
2023-07-03 12:53 ` Spencer Baugh
2023-07-03 13:16 ` Eli Zaretskii
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=83o7ktm8er.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64425@debbugs.gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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 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.