unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: StrawberryTea <look@strawberrytea.xyz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69107@debbugs.gnu.org
Subject: bug#69107: 30.0.50; mouse movement commands exit repeat maps
Date: Tue, 13 Feb 2024 13:54:45 -0600	[thread overview]
Message-ID: <87y1bo5e5e.fsf@strawberrytea.xyz> (raw)
In-Reply-To: <86il2sp2jl.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]

Thanks, I just finally realized that I can map mouse movement to nil.

(after! lsp-ui-doc
  (map! :map lsp-ui-doc-mode-map
        “<mouse-movement>” nil))

I never use that feature so this worked fine for me rather than digging into why
the <mouse-movement> events were being generated.

Thank you,
StrawberryTea
Eli Zaretskii <eliz@gnu.org> writes:

>> 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:54 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
2024-02-13 19:54   ` StrawberryTea [this message]
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

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