From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: michael_heerdegen@web.de, Eli Zaretskii <eliz@gnu.org>,
57163-done@debbugs.gnu.org
Subject: bug#57163: completing-read not allow cycling of the options by default
Date: Tue, 16 Aug 2022 05:07:36 +0000 [thread overview]
Message-ID: <Eepvh5IUNC_x6ofz52-dRjwO4ahH697slUu2wn2saSvOEK3DNe8gA9SkoXIbjbS3q0gaGG82bcljd8zorSt2zrH-2W_NNlQUcjLZGQmS0jk=@proton.me> (raw)
In-Reply-To: <Yvshk9ZT4tBMSNJb@protected.localdomain>
------- Original Message -------
On Tuesday, August 16th, 2022 at 4:48 AM, Jean Louis <bugs@gnu.support> wrote:
> * uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors bug-gnu-emacs@gnu.org [2022-08-14 19:16]:
>
> > Expecting the reading of entire chapters, and then having to
> > associate commands under different headings to different
> > functionalities is a failing strategy.
>
>
> Main obstacles in learning are misunderstood words. If there is any
> word you do not understand, ask for its meaning or try to find out its
> meaning, use dictionary, that way you may understand full sentences
> and its meanings.
>
> --
> Jean
Appropriate functionality should be discussed as soon as it becomes relevant, not at much later
stages. For the Emacs Manual, I cannot see description of what keys are available for use with
the minibuffer, particularly for completing-read, where options are available but there is no
clear way to know what key can move through the options. Keys for displaying history is quite
different from normal usage where there might not exist previous history.
prev parent reply other threads:[~2022-08-16 5:07 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
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 [this message]
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='Eepvh5IUNC_x6ofz52-dRjwO4ahH697slUu2wn2saSvOEK3DNe8gA9SkoXIbjbS3q0gaGG82bcljd8zorSt2zrH-2W_NNlQUcjLZGQmS0jk=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=57163-done@debbugs.gnu.org \
--cc=bugs@gnu.support \
--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).