From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: sbaugh@catern.com, 64425@debbugs.gnu.org
Subject: bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help
Date: Mon, 03 Jul 2023 16:16:38 +0300 [thread overview]
Message-ID: <83r0ppm8y1.fsf@gnu.org> (raw)
In-Reply-To: <ier5y7117ig.fsf@janestreet.com> (message from Spencer Baugh on Mon, 03 Jul 2023 08:53:11 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: sbaugh@catern.com, 64425@debbugs.gnu.org
> Date: Mon, 03 Jul 2023 08:53:11 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
> >> From: sbaugh@catern.com
> >> Date: Sun, 02 Jul 2023 19:14:06 +0000 (UTC)
> >> Cc: 64425@debbugs.gnu.org
> >>
> >> > Isn't this text too long for a single screen line? If so, it will
> >> > cause an annoying "jumping" of the mode line.
> >>
> >> Good point, how about this wording:
> >
> > OK, I think.
> >
> >> > Also, what about updating the documentation?
> >>
> >> All the other relevant documentation that I know about has already been
> >> updated to mention minibuffer-{next,previous,choose}-completion.
> >
> > I don't see the additional bindings documented anywhere.
> > And neither can I find any reference to
> > minibuffer-{next,previous,choose}-completion. What did I miss?
>
> (info "(emacs) Completion Commands") documents M-<DOWN>, M-<UP>,
> M-<RET>.
Ugh, not indexed, and the command names aren't even mentioned... How
are people supposed to find them? Now fixed.
> How about this?
>
> 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?
next prev parent reply other threads:[~2023-07-03 13:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:31 bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help 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 [this message]
[not found] <4beb74b6-6bbc-4e0f-9b95-f95b7edf79b9@email.android.com>
2023-07-03 13:28 ` Eli Zaretskii
2023-07-03 13:31 ` 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
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r0ppm8y1.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).