From: jaime.escalante@gmx.com
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48764@debbugs.gnu.org
Subject: bug#48764: mini-buffer completion
Date: Tue, 1 Jun 2021 17:54:51 +0200 [thread overview]
Message-ID: <trinity-e00820e1-5d74-43d8-9dd6-1f1006efe7f6-1622562891403@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87fsy1bnlg.fsf@gnus.org>
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?
> Sent: Wednesday, June 02, 2021 at 3:39 AM
> From: "Lars Ingebrigtsen" <larsi@gnus.org>
> To: jaime.escalante@gmx.com
> Cc: 48764@debbugs.gnu.org
> Subject: Re: bug#48764: mini-buffer completion
>
> jaime.escalante@gmx.com writes:
>
> > But the mini-buffer does not provide the user with any indication that
> > he can use the "up" and "down" keys to navigate a list of settings.
> > It would be beneficial to introduce some kind of glyph or indicator in
> > the mini-buffer to make the user aware that arrow keys can be used,
> > and be described in the manual.
>
> It should not come as a surprise that basic navigation keys allow you to
> navigate basically.
>
> Closing.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
next prev parent reply other threads:[~2021-06-01 15:54 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 [this message]
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
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
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=trinity-e00820e1-5d74-43d8-9dd6-1f1006efe7f6-1622562891403@3c-app-mailcom-bs01 \
--to=jaime.escalante@gmx.com \
--cc=48764@debbugs.gnu.org \
--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 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).