GNU bug report logs - #57163
completing-read not allow cycling of the options by default

Previous Next

Package: emacs;

Reported by: uzibalqa <uzibalqa <at> proton.me>

Date: Fri, 12 Aug 2022 22:15:02 UTC

Severity: normal

Tags: moreinfo

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: uzibalqa <uzibalqa <at> proton.me>
Subject: bug#57163: closed (Re: bug#57163: completing-read not allow
 cycling of the options by default)
Date: Sun, 14 Aug 2022 05:57:02 +0000
[Message part 1 (text/plain, inline)]
Your bug report

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

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 57163 <at> debbugs.gnu.org.

-- 
57163: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57163
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Eli Zaretskii <eliz <at> gnu.org>
To: uzibalqa <uzibalqa <at> proton.me>
Cc: michael_heerdegen <at> web.de, 57163-done <at> debbugs.gnu.org
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 <at> proton.me>
> Cc: michael_heerdegen <at> web.de, 57163 <at> 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.

[Message part 3 (message/rfc822, inline)]
From: uzibalqa <uzibalqa <at> proton.me>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: completing-read not allow cycling of the options by default
Date: Fri, 12 Aug 2022 22:14:30 +0000
[Message part 4 (text/plain, inline)]
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,
[Message part 5 (text/html, inline)]

This bug report was last modified 2 years and 338 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.