From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: jaime.escalante@gmx.com
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 48764@debbugs.gnu.org
Subject: bug#48764: mini-buffer completion
Date: Tue, 01 Jun 2021 23:50:42 +0100 [thread overview]
Message-ID: <874kehi4hp.fsf@tcd.ie> (raw)
In-Reply-To: <trinity-3bc5a6e1-529e-4a13-b11b-3a4878bffc2e-1622581445236@3c-app-mailcom-bs03> (jaime.escalante@gmx.com's message of "Tue, 1 Jun 2021 23:04:05 +0200")
jaime.escalante@gmx.com writes:
>> Sent: Wednesday, June 02, 2021 at 8:46 AM
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> To: jaime.escalante@gmx.com
>> Cc: "Lars Ingebrigtsen" <larsi@gnus.org>, 48764@debbugs.gnu.org
>> Subject: bug#48764: mini-buffer completion
>>
>> jaime.escalante@gmx.com writes:
>>
>> > How about mini-buffer entries that require user writing a string. How would
>> > a user figure out what to do?
>> >
>> > Is there any information about basic navigation keys for mini-buffer input in the manual?
>>
>> Does the node (info "(emacs) Minibuffer History")[1] in the Emacs manual
>> count? FWIW, it can be found through index entries such as 'minibuffer
>> history', 'M-n (minibuffer history)', 'DOWN (minibuffer history)', etc.
>
> We are not really talking about mini-buffer history, but mini-buffer input.
The OP refers to <up> and <down>. In the minibuffer, these keys by
default navigate so-called "minibuffer history", where e.g. <down>
inserts "future" history, AKA the next default value. So <down> is
actually "navigating" the list of defaults (completing-read's 7th
argument), not the list of completions (completing-read's 2nd argument).
If this is not the kind of input you're referring to, then could you
please clarify which input you're referring to?
>> For more details on minibuffer keymaps there's also
>> (info "(emacs) Minibuffer Maps")[2], found e.g. via the index entry
>> 'C-h r i minibuffer key TAB RET'.
>>
>> [1]: https://www.gnu.org/software/emacs/manual/html_node/emacs/Minibuffer-History.html
>> [2]: https://www.gnu.org/software/emacs/manual/html_node/emacs/Minibuffer-Maps.html
>>
>> HTH,
--
Basil
next prev parent reply other threads:[~2021-06-01 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 20:16 bug#48764: mini-buffer completion jaime.escalante
2021-06-01 15:39 ` Lars Ingebrigtsen
2021-06-01 15:54 ` jaime.escalante
2021-06-01 20:46 ` Basil L. Contovounesios
2021-06-01 21:00 ` jaime.escalante
2021-06-01 22:50 ` Basil L. Contovounesios
2021-06-01 23:00 ` jaime.escalante
2021-06-01 21:04 ` jaime.escalante
2021-06-01 22:50 ` Basil L. Contovounesios [this message]
2021-06-01 23:04 ` jaime.escalante
2021-06-01 21:31 ` bug#48764: [External] : " Drew Adams
2021-06-01 16:00 ` Drew Adams
2021-06-01 16:06 ` jaime.escalante
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=874kehi4hp.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=48764@debbugs.gnu.org \
--cc=jaime.escalante@gmx.com \
--cc=larsi@gnus.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.