bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help


From: Spencer Baugh
Subject: bug#64425: [PATCH] Mention minibuffer-next-completion in completion-help
Date: Mon, 03 Jul 2023 13:19:27 +0000 (UTC)

On Jul 3, 2023 09:16, Eli Zaretskii <eliz@gnu.org> wrote:

> 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?

Yes, my change adds bindings for them also in the completions buffer. So they can be used identically in both places.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]