unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28955@debbugs.gnu.org
Subject: bug#28955: 27.0.50; mouse event translation loses parameters
Date: Mon, 15 Jul 2019 12:58:50 -0400	[thread overview]
Message-ID: <m1ims39qut.fsf@gnu.org> (raw)
In-Reply-To: <87zhlguvw4.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sun, 14 Jul 2019 23:52:11 +0200")

> * Lars Ingebrigtsen <ynefv@tahf.bet> [2019-07-14 23:52:11 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> (define-key key-translation-map (kbd "<s-mouse-1>") (kbd "<mouse-2>"))
>>
>> Alas, when I actually do command-mouse-1, I get an error:
>>
>> Debugger entered--Lisp error: (error "mouse-yank-primary must be bound
>> to an event with parameters")
>>   call-interactively(mouse-yank-primary nil nil)
>>   command-execute(mouse-yank-primary)
>>
>>
>> Charles writes:
>>
>> When you add the key translation and type s-mouse-1, the mouse click
>> event ends up losing its location information.
>>
>> For example, the following:
>>
>> (s-mouse-1 (#<window 3 on *scratch*> 227 (116 . 92) 143676325 nil 227
>> (16 . 5) nil (116 . 12) (7 . 16)))
>>
>> gets turned into just:
>>
>> mouse-2
>>
>> which leads to the error about the missing parameters.
>
> I'm not quite sure what the test case is here, but if I do this:
>
> (progn
>   (define-key key-translation-map (kbd "<s-mouse-1>") (kbd "<mouse-2>"))
>   (insert (format "%S" (read-event))))
> =>
> (S-down-mouse-1 (#<window 4 on *Minibuf-0*> 1 (322 . 8) 1947797915 nil 1
> (21 . 0) nil (322 . 8) (15 . 29)))
>
> then things look pretty normal, I think?  So (unless this has fixed in
> the meantime), how does one reproduce the error?

Either of the following:

```
(define-key key-translation-map (kbd "<s-mouse-1>") (kbd "<mouse-2>"))
```

or

```
(define-key function-key-map (kbd "<s-mouse-1>") (kbd "<mouse-2>"))
```

exhibit the same behavior:

1. `C-u C-h c s-mouse-1` ==>
```
   <mouse-2> (translated from <s-down-mouse-1> <s-mouse-1>) at that spot
   runs the command mouse-yank-primary
```

2. Actually clicking s-mouse-1:
```
Debugger entered--Lisp error: (error "mouse-yank-primary must be bound to an event with ...")
  call-interactively(mouse-yank-primary nil nil)
  command-execute(mouse-yank-primary)
```


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1671
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
http://mideasttruth.com http://www.dhimmitude.org http://camera.org
Those who can't write, write manuals.





  reply	other threads:[~2019-07-15 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 14:44 bug#28955: 27.0.50; mouse event translation loses parameters Sam Steingold
2019-07-14 21:52 ` Lars Ingebrigtsen
2019-07-15 16:58   ` Sam Steingold [this message]
2019-07-15 17:04     ` Lars Ingebrigtsen

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=m1ims39qut.fsf@gnu.org \
    --to=sds@gnu.org \
    --cc=28955@debbugs.gnu.org \
    --cc=larsi@gnus.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).