all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 25 Nov 2021 04:32:26 +0100 (CET)	[thread overview]
Message-ID: <MpK7CpY--3-2@tutanota.com> (raw)
In-Reply-To: <86sfvpxmhn.fsf@mail.linkov.net>

22 Nov 2021, 02:19 by juri@linkov.net:

Hi Juri,

> I tried to implement what you asked to do, but got horrible results
> caused too much damage. Here is the lossage explaining the problem:
>
> C-<tab> ;; tab-next
> o ;; tab-next
> n ;; gnus-group-next-unread-group
>
> i.e. I typed C-<tab> to switch to the next tab with the text buffer
> where I started to type text that begins with the letters "on..."
>
> But instead of inserting letters to the buffer, the letter "o"
> switched to the second next tab. This tab contained the Gnus buffer
> where typing the second letter "n" called the bound command
> gnus-group-next-unread-group, and I lost all unread messages.
>
> But I never had such a problem when the repeating sequence was
> activated only by 'C-x t o ... o o ...' instead of 'C-<tab> o o o ...'
> because 'C-<tab>' is a single key, there is no need to activate
> other keys doing the same.
>
> This means that by default this behavior should be disabled.
> But maybe a new variable should allow to skip this check:

Yes,  you are right, it is disruptive.  Having tried the repeat-map I
had in the OP for a while now, it is biting me in the back in the most
unexpected times.  Maybe this is better left unimplemented?







  parent reply	other threads:[~2021-11-25  3:32 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MpK7CpY--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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.