From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>,
"51281@debbugs.gnu.org" <51281@debbugs.gnu.org>
Subject: bug#51281: [External] : bug#51281: 28.0.60; repeat-mode issues
Date: Wed, 20 Oct 2021 18:59:35 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883DA1B5649D168580A4D6F3BE9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y26ny56p.fsf@mail.linkov.net>
> > Currently there is a bug where the prefix arg changed for the
> > repeatable commands, is applied to the next non-repeatable
> > command. For example: C-- C-x o o C-n or C-x o C-- o C-n
>
> Actually, this too confusing feature
It's not confusing at all.
> that allows changing prefix args during the repeating
> sequence increases code complexity enormously.
Too bad. In that case, feel free to revert the changes
you've made that impose such complexity. The code just
worked - has worked for a long time.
> this feature will be removed (unless someone will ask
> to leave it)
"unless someone..."
Yes, I ask that this important feature be kept,
not lost. Users should continue to be able to
add/change a prefix arg (of any kind) at any
time during repetition.
Starting the command over (with a different
prefix arg) is not _at all_ the same thing as
continuing the command invocation.
(Think command state, and Emacs state in general,
in addition to user interaction.)
next prev parent reply other threads:[~2021-10-20 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 7:12 bug#51281: 28.0.60; repeat-mode issues Juri Linkov
2021-10-20 17:30 ` Juri Linkov
2021-10-20 18:59 ` Drew Adams [this message]
2021-10-21 16:51 ` bug#51281: [External] : " Juri Linkov
2021-10-21 17:09 ` Drew Adams
2021-11-04 23:24 ` Lars Ingebrigtsen
2021-12-01 17:58 ` Juri Linkov
2021-12-01 18:15 ` Eli Zaretskii
2022-09-05 19:40 ` bug#55986: 28.1; (setq repeat-keep-prefix t) breaks repeat-mode Lars Ingebrigtsen
2022-10-03 19:58 ` Juri Linkov
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=SJ0PR10MB54883DA1B5649D168580A4D6F3BE9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=51281@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).