From: Eli Zaretskii <eliz@gnu.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: michael_heerdegen@web.de, 57163@debbugs.gnu.org
Subject: bug#57163: completing-read not allow cycling of the options by default
Date: Sun, 14 Aug 2022 19:18:23 +0300 [thread overview]
Message-ID: <83mtc6kddc.fsf@gnu.org> (raw)
In-Reply-To: <-qQFoEYeOk9XtGrbenYCxKUz2BqvVEvFF8l_HqKxq3MGYVe1uxGsefA6PjnOHKZ_VfiNQlPCHafcmCoVvgmYeGCLIGZKttqd2FPRK_1WqPk=@proton.me> (message from uzibalqa on Sun, 14 Aug 2022 16:14:40 +0000)
> Date: Sun, 14 Aug 2022 16:14:40 +0000
> From: uzibalqa <uzibalqa@proton.me>
> Cc: michael_heerdegen@web.de, 57163-done@debbugs.gnu.org
>
> > 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.
next prev parent reply other threads:[~2022-08-14 16:18 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 [this message]
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=83mtc6kddc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57163@debbugs.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).