unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 57163-done@debbugs.gnu.org
Subject: bug#57163: completing-read not allow cycling of the options by default
Date: Sun, 14 Aug 2022 16:14:40 +0000	[thread overview]
Message-ID: <-qQFoEYeOk9XtGrbenYCxKUz2BqvVEvFF8l_HqKxq3MGYVe1uxGsefA6PjnOHKZ_VfiNQlPCHafcmCoVvgmYeGCLIGZKttqd2FPRK_1WqPk=@proton.me> (raw)
In-Reply-To: <83k07bl66z.fsf@gnu.org>

------- Original Message -------
On Sunday, August 14th, 2022 at 5:55 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Sat, 13 Aug 2022 19:31:39 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: michael_heerdegen@web.de, 57163@debbugs.gnu.org
> >
> > > > Cannot see <UP> and <DOWN> arrow keys described in "8.1 Using the Minibuffer" or after that.
> > >
> > > Wrong place. Look in "Minibuffer History".
> >
> > I have a problem with that, because I cannot see how someone reading "Minibuffer History"
> > would associate those commands with moving through the options when using the minibuffer.
> >
> > For many users, information listing the key-associated commands that can be employed when using
> > the minibuffer, is more useful in the part "8.1 Using the Minibuffer", rather than finding it much
> > much later and within the context of minibuffer history.
>
>
> Well, you are supposed to read the entire chapter, not just one
> section. Reading a single section is for those who know what they are
> after, and get to the section via the index entries.

Expecting the reading of entire chapters, and then having to associate
commands under different headings to different functionalities is a failing
strategy.

> Anyway, I've now added an explicit reference to completion to the text
> in "Minibuffer History", and also added an index entry about
> walking through completion candidates, leading there.

> And with that, I'm closing this bug report.
>





  reply	other threads:[~2022-08-14 16:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 22:14 bug#57163: completing-read not allow cycling of the options by default uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13  4:52 ` Michael Heerdegen
2022-08-13  6:01   ` Eli Zaretskii
2022-08-13 14:32     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 15:14       ` Eli Zaretskii
2022-08-13 16:09         ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 17:21           ` Eli Zaretskii
2022-08-13 18:15             ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 18:20               ` Eli Zaretskii
2022-08-13 18:28                 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 18:46                   ` Eli Zaretskii
2022-08-13 19:31                     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14  5:55                       ` Eli Zaretskii
2022-08-14 16:14                         ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-14 16:18                           ` Eli Zaretskii
2022-08-14 16:34                             ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-14 16:51                               ` Eli Zaretskii
2022-08-14 17:11                                 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16  5:24                               ` Jean Louis
2022-08-16  4:48                           ` Jean Louis
2022-08-16  5:07                             ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='-qQFoEYeOk9XtGrbenYCxKUz2BqvVEvFF8l_HqKxq3MGYVe1uxGsefA6PjnOHKZ_VfiNQlPCHafcmCoVvgmYeGCLIGZKttqd2FPRK_1WqPk=@proton.me' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57163-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=uzibalqa@proton.me \
    /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).