From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: sbaugh@catern.com, emacs-devel@gnu.org
Subject: Re: Navigating completions from minibuffer
Date: Fri, 08 Dec 2023 10:46:31 +0200 [thread overview]
Message-ID: <834jgt13q0.fsf@gnu.org> (raw)
In-Reply-To: <86a5qmihhu.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 07 Dec 2023 09:44:45 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: sbaugh@catern.com, emacs-devel@gnu.org
> Date: Thu, 07 Dec 2023 09:44:45 +0200
>
> >> > *** Selected completion candidates are deselected on typing.
> >> > When a user types, point in the *Completions* window will be moved off
> >> > any completion candidates. 'minibuffer-choose-completion' ('M-RET')
> >> > will still choose a previously-selected completion candidate, but the
> >> > new command 'minibuffer-choose-completion-or-exit' (bound by
> >> > 'minibuffer-visible-completions') will exit with the minibuffer
> >> > contents instead. The deselection behavior can be controlled with the
> >> > new user option 'completion-auto-deselect'.
> >> >
> >> > What are "selected completion candidates"? I typed "C-x C-f TAB", and
> >> > Emacs popped the completions buffer, but without "selecting" any of
> >> > the candidates. Searching for "select" in the buffer produced by
> >> > "M-x apropos complet RET" doesn't seem to find anything pertinent.
> >> > And there's nothing about this in the manual. What am I missing?
> >>
> >> Maybe a better term would be "a highlighted completion candidate"?
> >> This should denote a candidate where point is located in the
> >> *Completions* buffer.
> >
> > Thanks, but I still don't think I follow. How do I get this situation
> > where a completion candidate is "highlighted" or "selected", starting
> > from typing a command like "C-x C-f" and then typing TAB?
>
> C-x C-f TAB TAB M-<down>
>
> Then e.g. DEL (<backspace>) will "deselect" the highlighted candidate.
Thanks, I tried to improve the documentation using the above
information.
Btw, I notice (with some sadness) that we are largely back to our
previous practice of not updating the manuals with information about
changes. This has two adverse consequences:
. the release cycle of the next major release will take longer
. the manuals included in the next major release are more likely to
be inaccurate and/or incomplete
People who complain about too slow release schedule of Emacs should
take note, and hopefully invest more effort in the future in updating
the documentation together with code changes.
prev parent reply other threads:[~2023-12-08 8:46 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 3:57 Navigating completions from minibuffer T.V Raman
2023-11-07 4:55 ` T.V Raman
2023-11-07 7:20 ` Juri Linkov
2023-11-07 17:53 ` T.V Raman
2023-11-07 19:36 ` T.V Raman
2023-11-08 7:39 ` Juri Linkov
2023-11-08 16:21 ` T.V Raman
2023-11-08 17:18 ` T.V Raman
2023-11-08 22:11 ` Slow completion-at-point was " T.V Raman
2023-11-09 7:22 ` Slow completion-at-point Juri Linkov
2023-11-09 12:10 ` Dmitry Gutov
2023-11-09 16:20 ` Juri Linkov
2023-11-09 18:32 ` João Távora
2023-11-11 2:48 ` T.V Raman
2023-11-11 10:36 ` Dmitry Gutov
2023-11-11 16:40 ` T.V Raman
2023-11-11 19:00 ` Juri Linkov
2023-11-11 19:43 ` T.V Raman
2023-11-11 21:50 ` Dmitry Gutov
2023-11-09 15:39 ` T.V Raman
2023-11-09 12:20 ` Slow completion-at-point was Re: Navigating completions from minibuffer Dmitry Gutov
2023-11-09 15:41 ` T.V Raman
2023-11-09 17:46 ` T.V Raman
2023-11-10 13:12 ` Spencer Baugh
2023-11-11 18:58 ` Juri Linkov
2023-11-14 7:36 ` Juri Linkov
2023-11-15 21:40 ` Spencer Baugh
2023-11-16 17:15 ` T.V Raman
2023-11-15 22:03 ` Spencer Baugh
2023-11-16 7:16 ` Juri Linkov
2023-11-16 14:41 ` Spencer Baugh
2023-11-16 17:28 ` Juri Linkov
2023-11-16 18:25 ` Spencer Baugh
2023-11-17 7:09 ` Juri Linkov
2023-11-17 17:22 ` Spencer Baugh
2023-11-18 20:58 ` sbaugh
2023-11-19 7:08 ` Juri Linkov
2023-11-19 8:19 ` Eli Zaretskii
2023-11-19 14:41 ` Spencer Baugh
2023-11-19 18:01 ` Juri Linkov
2023-11-19 19:41 ` Spencer Baugh
2023-11-20 2:58 ` Spencer Baugh
2023-11-23 13:39 ` sbaugh
2023-11-24 7:54 ` Juri Linkov
2023-11-25 15:19 ` Spencer Baugh
2023-11-25 16:08 ` Eli Zaretskii
2023-11-25 18:23 ` sbaugh
2023-11-25 18:48 ` Juri Linkov
2023-11-26 13:10 ` sbaugh
2023-11-25 19:00 ` Eli Zaretskii
2023-11-25 17:46 ` Juri Linkov
2023-11-26 14:33 ` Spencer Baugh
2023-11-27 7:22 ` Juri Linkov
2023-11-28 14:48 ` Spencer Baugh
2023-11-28 17:23 ` Juri Linkov
2023-11-29 0:20 ` Spencer Baugh
2023-12-03 17:21 ` Juri Linkov
2023-12-03 18:13 ` Eli Zaretskii
2023-12-06 17:20 ` Juri Linkov
2023-12-06 17:50 ` Eli Zaretskii
2023-12-07 7:44 ` Juri Linkov
2023-12-08 8:46 ` Eli Zaretskii [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.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=834jgt13q0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=sbaugh@catern.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).