From: Jonathan Ganc <jonganc@gmail.com>
To: martin rudalics <rudalics@gmx.at>, 26104@debbugs.gnu.org
Subject: bug#26104: 26.0.50; In Ubuntu, having mouse over other frame cause Alt key to produce a <switch-frame> event
Date: Sat, 8 Apr 2017 18:42:11 -0400 [thread overview]
Message-ID: <2ecfca67-9713-7a0d-7e56-b5801242f782@gmail.com> (raw)
In-Reply-To: <58E8A68E.70603@gmx.at>
On 04/08/2017 04:59 AM, martin rudalics wrote:
> And what would make you that sure that the `handle-switch-frame' event
> was not inserted before you disabled xinput?
I used both yank and then yank-pop after I disabled the xinput. But
also, I can see that read-event gives switch-frame every time I press
alt. But you are clearly correct in that the mouse/cursor plays an
important role, since it only happens when the cursor is in a particular
position.
>
> Anyway, as a first attempt try to apply the attached patch to keyboard.c
> and tell me what the value of the variable `lispy-switch-frame-source'
> is when you try your M-y.
>
> martin
I changed keyboard.c and rebuilt emacs. The value for
lispy-switch-frame-source is focus_in_event.
next prev parent reply other threads:[~2017-04-08 22:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 3:25 bug#26104: 26.0.50; In Ubuntu, having mouse over other frame cause Alt key to produce a <switch-frame> event Jonathan Ganc
2017-03-17 7:19 ` martin rudalics
2017-03-18 1:04 ` Jonathan Ganc
2017-03-18 8:19 ` martin rudalics
2017-04-01 9:53 ` martin rudalics
2017-04-04 0:59 ` Jonathan Ganc
2017-04-05 6:58 ` martin rudalics
2017-04-07 3:56 ` Jonathan Ganc
2017-04-07 5:56 ` martin rudalics
2017-04-07 15:27 ` Jonathan Ganc
2017-04-08 8:59 ` martin rudalics
2017-04-08 22:42 ` Jonathan Ganc [this message]
2017-04-09 6:37 ` martin rudalics
2017-04-15 9:41 ` Jonathan Ganc
2017-04-15 14:50 ` martin rudalics
2017-04-15 15:11 ` Eli Zaretskii
2017-04-15 19:39 ` martin rudalics
2017-04-15 20:23 ` Jonathan Ganc
2017-04-16 7:15 ` martin rudalics
2017-04-15 20:33 ` Jonathan Ganc
2022-04-21 15:15 ` 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=2ecfca67-9713-7a0d-7e56-b5801242f782@gmail.com \
--to=jonganc@gmail.com \
--cc=26104@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).