emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57163: closed (completing-read not allow cycling of the options by d


From: GNU bug Tracking System
Subject: bug#57163: closed (completing-read not allow cycling of the options by default)
Date: Sun, 14 Aug 2022 05:57:02 +0000

Your message dated Sun, 14 Aug 2022 08:55:48 +0300
with message-id <83k07bl66z.fsf@gnu.org>
and subject line Re: bug#57163: completing-read not allow cycling of the 
options by default
has caused the debbugs.gnu.org bug report #57163,
regarding completing-read not allow cycling of the options by default
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57163: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57163
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: completing-read not allow cycling of the options by default Date: Fri, 12 Aug 2022 22:14:30 +0000

Why is it that things like completing-read not allow cycling of the options by default?  Especially for new user, not having the ability to cycle by default is a terrible plan,



--- End Message ---
--- Begin Message --- Subject: Re: bug#57163: completing-read not allow cycling of the options by default Date: Sun, 14 Aug 2022 08:55:48 +0300
> 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.

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.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]