unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 16 Nov 2021 22:18:17 +0200	[thread overview]
Message-ID: <86r1bfoowu.fsf@mail.linkov.net> (raw)
In-Reply-To: <Mobub4z--3-2@tutanota.com> (visuwesh@tutanota.com's message of "Tue, 16 Nov 2021 09:43:36 +0100 (CET)")

> I think implementing this will actually end up making certain repeat-maps
> tedious to use.  One example that comes to mind is
> `outline-navigation-repeat-map' where it is quite easy to misfire f/b
> when you actually want n/p.  Starting the map again with C-c @ C-n is
> quite tedious.  I hope you reconsider this, or make the current
> behaviour opt-in.

Please clarify how can you misfire f/b when you intended n/p.
What keys does your keymap contain?

> Although triggering repeat-map on error is strange for the scenario in
> OP, I hope the above convinces you regardless.  I only noticed the
> behaviour on error is desirable after I started using the outline functions
> a bit more.

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.





  reply	other threads:[~2021-11-16 20:18 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 [this message]
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
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=86r1bfoowu.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).