From: Juri Linkov <juri@linkov.net>
To: Visuwesh <visuwesh@tutanota.com>
Cc: 51390 <51390@debbugs.gnu.org>
Subject: bug#51390: 29.0.50; repeat-mode: Fails to repeat keys in global-map(?)
Date: Wed, 17 Nov 2021 09:54:55 +0200 [thread overview]
Message-ID: <8635nv9rtc.fsf@mail.linkov.net> (raw)
In-Reply-To: <Mof_1ES--3-2@tutanota.com> (visuwesh@tutanota.com's message of "Wed, 17 Nov 2021 02:47:49 +0100 (CET)")
> When you do not know the structure of the outline headings beforehand,
> it can so happen that you press f/b anticipating that there's a heading
> on the same level but that might not be case. If f/b `error's, then you
> have to press n/p to continue navigating. This is what I meant by
> "misfiring."
>
> If repeat-mode decides to end the repeating sequence, I'd have to start
> again with C-c @ C-n. IMO, this isn't a friendly interface.
>
>>Triggering repeat-map on error is a bug that will be fixed.
>>But it will be fixed in such a way that the error will exit
>>the repeating sequence.
>
> My point is that sometimes it is desirable to not end the sequence on
> `error'.
Thanks, everything's clear now. And no worries — a new option will allow
to not end the repeating sequence on error.
One problem I had with writing tests for such a feature — tests for repeat-mode
are based on ‘execute-kbd-macro’, but an error ends the keyboard macro.
So probably there will be no tests for this error-signaling repeatable commands.
next prev parent reply other threads:[~2021-11-17 7:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 16:32 bug#51390: 29.0.50; repeat-mode: Fails to repeat keys in global-map(?) Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 17:16 ` Juri Linkov
2021-10-25 17:26 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 17:41 ` Juri Linkov
2021-11-15 18:54 ` Juri Linkov
2021-11-16 8:43 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 20:18 ` Juri Linkov
2021-11-17 1:47 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-17 7:54 ` Juri Linkov [this message]
2021-11-20 13:23 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-20 19:12 ` Juri Linkov
2021-11-21 2:21 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-21 20:49 ` Juri Linkov
2021-11-22 3:44 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-22 3:45 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 3:32 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 7:54 ` Juri Linkov
2021-11-25 8:11 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 19:09 ` Juri Linkov
2021-12-02 10:23 ` Visuwesh 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=8635nv9rtc.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=51390@debbugs.gnu.org \
--cc=visuwesh@tutanota.com \
/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).