Subject: bug#57163: completing-read not allow cycling of the options by default

From: uzibalqa <[email-masked]>
Date: Sun, 14 Aug 2022 16:34:42 +0000

Sent with Proton Mail secure email.

------- Original Message -------
On Sunday, August 14th, 2022 at 4:18 PM, Eli Zaretskii <[email-masked]> wrote:

> > Date: Sun, 14 Aug 2022 16:14:40 +0000
> > From: uzibalqa [email-masked]
> > Cc: [email-masked], [email-masked]
> >
> > > 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.
>
>
> That's the recommended practice of learning about this subject when
> you are not familiar with it (as you seem to be). Reading single
> sections in this situation is not a very effective way of learning
> about this.

Completion is defined as a feature that fills in the rest of a name starting from an
abbreviation for it.  Easily leads to confusion because one does not commonly associate
completion with next selection element.

Have looked at "Variable: minibuffer-local-map" which states that it is the default local keymap for reading from the minibuffer. By default, it makes the following bindings:

But that list is not complete because it associates M-n and M-p only with history elements.