From: Bozhidar Batsov <bozhidar@batsov.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Brian Jenkins <brian@brianjenkins.org>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] frame.c: focus hooks
Date: Tue, 19 Nov 2013 16:10:00 +0200 [thread overview]
Message-ID: <CAM9Zgm2HKTTYm8o7ne3aSh1=ecVHKARnk_eOAYg7+C+KaESViQ@mail.gmail.com> (raw)
In-Reply-To: <87mwl0g5kw.fsf@uwakimon.sk.tsukuba.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
Btw, it would be good if this change was mentioned in the NEWS, since I'm
pretty sure I'm not the only Emacs user that will find it useful :-)
On 19 November 2013 10:26, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> Brian Jenkins writes:
>
> > It's not clear to me that X itself even *has* a concept of "active
> > application" distinct from "frame that has input focus".
>
> No, it doesn't, and it can't.
>
> Multiple applications can select events in the same X window at the same
> time. For example, the classic debugging tool xev(1) selects events on
> a window you select (say, an Emacs frame), and outputs a trace of those
> events. Which is active: xev, or Emacs (which also receives those input
> events and acts on them as if xev didn't exist)?
>
> The only sane answer is "both of them".
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1260 bytes --]
next prev parent reply other threads:[~2013-11-19 14:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 17:50 [PATCH] frame.c: focus hooks Brian Jenkins
2013-11-17 18:29 ` Bozhidar Batsov
2013-11-17 22:25 ` Brian Jenkins
2013-11-17 22:33 ` Drew Adams
2013-11-18 13:24 ` Brian Jenkins
2013-11-18 14:53 ` Drew Adams
2013-11-19 0:19 ` Stefan Monnier
2013-11-19 8:26 ` Stephen J. Turnbull
2013-11-19 14:10 ` Bozhidar Batsov [this message]
2013-11-20 3:10 ` Brian Jenkins
2013-11-18 8:20 ` Bozhidar Batsov
2013-11-18 13:32 ` Stefan Monnier
[not found] ` <CAM9Zgm18uL7+PJ+60NjZqtjZJ6tUV77xUbFhXh7UPwqs==1=hg@mail.gmail.com>
2013-11-18 14:20 ` Fwd: " Bozhidar Batsov
2013-11-18 14:23 ` Brian Jenkins
2013-11-18 18:44 ` Richard Stallman
2013-11-18 19:49 ` Brian Jenkins
2013-11-19 6:02 ` Richard Stallman
2013-11-19 18:14 ` Brian Jenkins
2013-11-19 18:53 ` Drew Adams
2013-11-20 0:52 ` Brian Jenkins
2013-11-19 23:42 ` Richard Stallman
2013-11-20 0:52 ` Josh
2013-11-20 3:16 ` Stefan Monnier
2013-11-20 3:36 ` Josh
2013-11-20 7:34 ` martin rudalics
2014-01-09 17:01 ` Josh
2014-01-11 10:25 ` martin rudalics
2014-01-11 19:05 ` Josh
2014-01-12 9:54 ` martin rudalics
2014-01-14 17:30 ` Josh
2014-01-14 18:10 ` martin rudalics
2014-01-10 17:31 ` Stefan Monnier
2014-01-11 19:06 ` Josh
2013-11-20 0:53 ` Brian Jenkins
2013-11-20 7:46 ` Jarek Czekalski
2013-11-17 19:28 ` Glenn Morris
2013-11-17 21:19 ` Stefan Monnier
2013-11-18 4:11 ` Leo Liu
[not found] ` <CADTx1Oy5pUmb9sPU6jm0yt1hJtvgJmfDtZQpeFakmHknhEXE=A@mail.gmail.com>
2013-11-18 13:33 ` Fwd: " Brian Jenkins
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='CAM9Zgm2HKTTYm8o7ne3aSh1=ecVHKARnk_eOAYg7+C+KaESViQ@mail.gmail.com' \
--to=bozhidar@batsov.com \
--cc=brian@brianjenkins.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.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).