From: Visuwesh via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 51390 <51390@debbugs.gnu.org>
Subject: bug#51390: 29.0.50; repeat-mode: Fails to repeat keys in global-map(?)
Date: Sun, 21 Nov 2021 03:21:58 +0100 (CET) [thread overview]
Message-ID: <Mp-ICXY--3-2@tutanota.com> (raw)
In-Reply-To: <86fsrqptnp.fsf@mail.linkov.net>
21 Nov 2021, 00:42 by juri@linkov.net:
Hi Juri,
>>>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.
>>
>> I wonder if the new mechanism added to ERT by Lars could be help here?
>> (and used by the indentation tests) But I suppose you still have to end
>> up using keyboard macros one way or another...
>
> I don't know how buffer-based ERT fixtures could help to test repeatable
> key sequences. What I rather tried to do is to use ‘ert-simulate-command’
> (after removing ‘(cl-assert (not unread-command-events) t)’) and
> ‘ert-simulate-keys’ (after adding ‘(noninteractive nil)’ let-binding),
> to no avail.
I was thinking about grouping navigation commands that could `error'
(like in OP and the outline commands) in a repeatable keymap and making
use of Point-Char spec to test where the point ends up.
But I suppose this wouldn't get us anywhere since you still have to
"press" those keys somehow.
next prev parent reply other threads:[~2021-11-21 2:21 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
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 [this message]
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=Mp-ICXY--3-2@tutanota.com \
--to=bug-gnu-emacs@gnu.org \
--cc=51390@debbugs.gnu.org \
--cc=juri@linkov.net \
--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).