all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: StrawberryTea <look@strawberrytea.xyz>
Cc: 69107@debbugs.gnu.org
Subject: bug#69107: 30.0.50; mouse movement commands exit repeat maps
Date: Tue, 13 Feb 2024 21:49:50 +0200	[thread overview]
Message-ID: <86il2sp2jl.fsf@gnu.org> (raw)
In-Reply-To: <87zfw45gxd.fsf@strawberrytea.xyz> (message from StrawberryTea on Tue, 13 Feb 2024 12:53:18 -0600)

> From: StrawberryTea <look@strawberrytea.xyz>
> Date: Tue, 13 Feb 2024 12:53:18 -0600
> 
> Hi. I'm using LSP mode which defines a <mouse-movement> command. I have
> noticed that in some special situation involving switching workspaces in
> Doom Emacs while using EXWM (Emacs X Window Manager), the
> <mouse-movement> command is triggered after switching workspaces which
> triggers the repeat map to exit even though the mouse wasn't actually
> visibly moved. I think it might be reasonable to exclude mouse movement
> commands from exiting the repeat map by default or as an option.

You can do that yourself for commands you want to repeat, can't you?
From the node "Creating Keymaps" in the ELisp Reference manual:

     Each command in the keymap can be marked as 'repeatable', i.e.
     usable in ‘repeat-mode’, by putting a ‘repeat-map’ property on it,
     e.g.

          (put 'undo 'repeat-map 'undo-repeat-map)

     where the value of the property is the map to be used by
     ‘repeat-mode’.

There's no way the default configuration can ever anticipate all of
the known and unknown commands that some users could want to be
repeatable.  But each user can add commands to the set of repeatable
ones by using the above technique.





  reply	other threads:[~2024-02-13 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 18:53 bug#69107: 30.0.50; mouse movement commands exit repeat maps StrawberryTea
2024-02-13 19:49 ` Eli Zaretskii [this message]
2024-02-13 19:54   ` StrawberryTea
2024-02-14 16:38     ` StrawberryTea

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=86il2sp2jl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69107@debbugs.gnu.org \
    --cc=look@strawberrytea.xyz \
    /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.