[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs-30 8064b2a6798: Document undocumented completion commands
From: |
Eshel Yaron |
Subject: |
Re: emacs-30 8064b2a6798: Document undocumented completion commands |
Date: |
Mon, 06 Jan 2025 13:16:40 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eshel Yaron <me@eshelyaron.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sun, 05 Jan 2025 12:36:27 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Eshel Yaron <me@eshelyaron.com>
>> >> Cc: Eli Zaretskii <eliz@gnu.org>
>> >> Date: Sun, 05 Jan 2025 09:06:04 +0100
>> >>
>> >> > DEFUN ("read-from-minibuffer", Fread_from_minibuffer,
>> >> > Sread_from_minibuffer, 1, 7, 0,
>> >> > doc: /* Read a string from the minibuffer, prompting with
>> >> > string PROMPT.
>> >> > +While in the minibuffer, you can use
>> >> > \\<minibuffer-local-completion-map>\\[minibuffer-complete] and
>> >> > \\[minibuffer-complete-word] to complete your input.
>> >>
>> >> This part isn't quite right: read-from-minibuffer does not provide
>> >> completion with minibuffer-complete[-word] by default.
>> >>
>> >> How about just dropping these references?
>> >
>> > Sorry, I don't want to drop them, they are important.
>> >
>> > Why do you say these are not supported by default? I can use them in
>> > "emacs -Q", so what did I miss?
>>
>> Hmm, C-h f read-from-minibuffer now says "While in the minibuffer, you can
>> use TAB and SPC to complete your input." But read-from-minibuffer doesn't
>> provide such completion, by default it uses minibuffer-local-map, in which
>> both keys are self-inserting. Do you see something different?
>
> Please help me make this accurate without losing the important
> information about these commands. Okay?
AFAICT it would be more accurate (and relevant) to mention these
commands in the docstring of completing-read, not read-from-minibuffer.
But they are also pretty well documented in both the Emacs manual and
the ELisp manual, so I'm not sure I see the importance of mentioning
them there as well...
Best,
Eshel
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eshel Yaron, 2025/01/05
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eli Zaretskii, 2025/01/05
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eshel Yaron, 2025/01/05
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eli Zaretskii, 2025/01/05
- Re: emacs-30 8064b2a6798: Document undocumented completion commands,
Eshel Yaron <=
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eli Zaretskii, 2025/01/09
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eshel Yaron, 2025/01/09
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eli Zaretskii, 2025/01/11
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Juri Linkov, 2025/01/11
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Eli Zaretskii, 2025/01/11
- Re: emacs-30 8064b2a6798: Document undocumented completion commands, Juri Linkov, 2025/01/12