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, 30 Nov 2021 21:09:28 +0200	[thread overview]
Message-ID: <86k0gpbh1j.fsf@mail.linkov.net> (raw)
In-Reply-To: <MpL8_rl--3-2@tutanota.com> (visuwesh@tutanota.com's message of "Thu, 25 Nov 2021 09:11:36 +0100 (CET)")

close 51390 28.0.60
thanks

>> This feature of checking the last key could be enabled per every keymap
>> using symbol properties.  Then you can disable it for one keymap,
>> while keeping enabled for all remaining keymaps.
>
> That indeed sounds like a good solution to the problem.  Thanks!

This is fixed now, so your original case is supported,
as well as more cases reported in e.g.
https://lists.gnu.org/archive/html/emacs-devel/2021-04/msg00083.html
https://lists.gnu.org/archive/html/emacs-devel/2021-08/msg00962.html

The behavior can be customized by the new user option 'repeat-check-key'.
Also a command can have a symbol property with the same name
and two values: 't' checks the key when the variable is nil,
and 'no' doesn't check the key when the variable is t.

A special property 'no' is necessary instead of using 'nil',
because 'get' can't distinguish when the property has the
value 'nil' and when there is no property set on the symbol.
Also there is no function to delete a property from a plist,
so every package invents own wheel, e.g. map--plist-delete.
org-plist-delete-all, svg--plist-delete...





  reply	other threads:[~2021-11-30 19:09 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
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 [this message]
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=86k0gpbh1j.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).