From: Drew Adams <drew.adams@oracle.com>
To: 64656@debbugs.gnu.org
Subject: bug#64656: 29.0.91; Doc of minibuffer histories and completing-read - automatic addition of completions to DEFAULT list
Date: Sat, 15 Jul 2023 23:35:20 +0000 [thread overview]
Message-ID: <SJ0PR10MB54884D179AB7032967B9D4C8F335A@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
It seems to me that the doc, including in the Elisp manual, doesn't make
clear that, by default, `completing-read' automatically adds the list of
all completions provided by the completion table to the list of
defaults, just after the default value. That is, by default, it calls
`minibuffer-default-add-completions'.
This is not obvious from reading the docs. For example, it's not
obvious that if you use `C-h v' and then `M-p', repeating `M-p, you get
the symbols that are variables, one by one, inserted into the
minibuffer.
How so? Because by default variable `minibuffer-default-add-function'
is `minibuffer-default-add-completions'. Again, none of this is
obvious. To find it out, a user needs to check what `M-p' is bound to,
then check the source code for that function, and then the source code
or the doc string of function `goto-history-element', which it calls.
In sum, important user-visible behavior isn't described in the manual or
the "top-level", most-relevant doc strings (e.g. `completing-read').
This is a request to, somehow, make this default behavior more apparent
in the doc. Thx.
In GNU Emacs 29.0.91 (build 2, x86_64-w64-mingw32) of 2023-05-14 built
on AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.19045
System Description: Microsoft Windows 10 Pro (v10.0.2009.19045.3086)
Configured using:
'configure --with-modules --without-dbus --with-native-compilation
--without-compress-install --with-tree-sitter CFLAGS=-O2'
Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS TREE_SITTER WEBP XPM ZLIB
(NATIVE_COMP present but libgccjit not available)
next reply other threads:[~2023-07-15 23:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 23:35 Drew Adams [this message]
2023-07-16 5:24 ` bug#64656: 29.0.91; Doc of minibuffer histories and completing-read - automatic addition of completions to DEFAULT list Eli Zaretskii
2023-07-16 14:34 ` Drew Adams
2023-07-16 14:58 ` Eli Zaretskii
2023-07-18 20:27 ` Drew Adams
2023-07-19 6:35 ` Juri Linkov
2023-07-19 17:23 ` Drew Adams
2023-10-20 6:47 ` Juri Linkov
2023-10-20 16:48 ` Drew Adams
2023-10-29 18:29 ` Juri Linkov
2023-10-29 22:15 ` Drew Adams
2023-10-30 7:44 ` Juri Linkov
2023-11-13 18:14 ` Drew Adams
2023-11-14 5:57 ` Thierry Volpiatto
2023-11-14 7:28 ` Juri Linkov
2023-11-05 18:11 ` Juri Linkov
2023-11-06 7:28 ` Juri Linkov
2023-11-09 16:34 ` Juri Linkov
2023-11-09 16:48 ` Eli Zaretskii
2023-11-09 17:03 ` Juri Linkov
2023-11-09 19:31 ` Eli Zaretskii
2023-11-10 7:45 ` Juri Linkov
2023-11-10 8:15 ` Eli Zaretskii
2023-11-12 8:13 ` Juri Linkov
2023-11-13 17:17 ` Juri Linkov
2023-11-13 18:14 ` Drew Adams
2023-11-14 7:30 ` Juri Linkov
2023-11-15 17:52 ` Juri Linkov
2023-11-10 19:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-20 6:19 ` Eli Zaretskii
2023-07-20 16:45 ` Drew Adams
2023-07-22 8:07 ` Eli Zaretskii
2023-07-16 13:40 ` Drew Adams
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=SJ0PR10MB54884D179AB7032967B9D4C8F335A@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=64656@debbugs.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.