unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Ganc <jonganc@gmail.com>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: 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, 15 Apr 2017 16:23:44 -0400	[thread overview]
Message-ID: <9f6f3cf5-77b6-3280-387d-084df287090f@gmail.com> (raw)
In-Reply-To: <58F276E1.1000405@gmx.at>

I'm currently trying to understand the issue better, but I think Compiz 
Settings just allows to access to more settings (I think Compiz is part 
of Unity; on my computer, there's always a compiz process). So I think 
it is actually preventing Ubuntu from sending the event when Alt is 
pressed, not intercepting Alt, i.e. it doesn't actively do anything.


On 04/15/2017 03:39 PM, martin rudalics wrote:
> > Heh, it looks like they copied the MS-Windows (mis)feature, whereby
> > tapping the Alt key activates the menu bar, which would indeed require
> > a focus-in event; seems like some GNU/Linux distros have joined this
> > lunacy.  In the MS-Windows build, we have w32-pass-alt-to-system to
> > control that.
>
> If I'm not mistaken, on MS-Windows you can activate the menu bar of a
> window via the Alt key iff that window has focus already.  I still fail
> to understand how pressing the Alt key could transfer focus to another
> window.
>
> > Perhaps we should generalize w32-pass-alt-to-system instead? Assuming
> > an application can control this behavior on GNU/Linux, that is.
>
> If Compiz can, Emacs should be able to do that too.
>
> martin






  reply	other threads:[~2017-04-15 20:23 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
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 [this message]
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=9f6f3cf5-77b6-3280-387d-084df287090f@gmail.com \
    --to=jonganc@gmail.com \
    --cc=26104@debbugs.gnu.org \
    --cc=eliz@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).