From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to determine (from Elisp) whether the Emacs frame has focus?
Date: Sat, 14 Nov 2015 13:34:06 +0100 [thread overview]
Message-ID: <871tbsbw01.fsf@mbork.pl> (raw)
In-Reply-To: <83d1vcexdp.fsf@gnu.org>
On 2015-11-14, at 10:36, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Random832 <random832@fastmail.com>
>> Date: Sat, 14 Nov 2015 03:36:03 -0500
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>> > I'm probably missing something very important, because I don't
>> > understand what you are looking for. The selected frame by definition
>> > has focus, at least AFAIK. What am I missing?
>>
>> Well that may be true who never leave their Emacs instance, but for the
>> rest of us some non-Emacs application might have focus instead.
>
> Ah, so he meant detect when some other application has focus? That's
> what I was missing, thanks.
>
> Then I don't understand why the solution of focus-in/out-hook was
> rejected as "hackish". These hooks are there precisely for situations
> like these, AFAIK. IMO, there's nothing hackish about that.
AFAIU, these hooks are best suited to situations like "run LaTeX on
switching to a pdf viewer". That does not require global variables; my
use case does.
Would it be possible to introduce a function like (emacs-has-focus-p)
for that? Would it make sense?
>> (Also I suspect by "selected" he meant a frame the programmer "selects"
>> to pass in to e.g. a function that answers the question, rather than
>> selected-frame.)
>
> I indeed feel there might still be aspects of the original question
> that need to be further clarified.
For starters, I only want to know whether it is Emacs which has focus or
not. Then, I would like to know e.g. the mode of the current buffer; in
that case, I'm not sure what I should do when the current buffer is the
minibuffer or something. But this is less important for me now.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-11-14 12:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 21:45 How to determine (from Elisp) whether the Emacs frame has focus? Marcin Borkowski
2015-11-14 3:48 ` Emanuel Berg
2015-11-14 4:05 ` John Mastro
2015-11-14 7:30 ` tomas
2015-11-14 8:44 ` Marcin Borkowski
2015-11-14 10:45 ` tomas
2015-11-14 20:28 ` Marcin Borkowski
2015-11-14 8:06 ` Eli Zaretskii
2015-11-14 8:36 ` Random832
2015-11-14 9:36 ` Eli Zaretskii
2015-11-14 12:34 ` Marcin Borkowski [this message]
2015-11-14 13:40 ` Eli Zaretskii
2015-11-15 7:45 ` Marcin Borkowski
2015-11-15 19:45 ` Eli Zaretskii
2015-11-16 14:08 ` Nicolas Richard
2015-11-16 16:58 ` Marcin Borkowski
2015-11-14 21:10 ` Stefan Monnier
2015-11-16 17:00 ` Marcin Borkowski
2015-11-14 8:42 ` Marcin Borkowski
2015-11-14 8:59 ` Eli Zaretskii
2015-11-14 10:54 ` Yuri Khan
2015-11-14 11:04 ` Eli Zaretskii
2015-11-14 8:44 ` Michael Heerdegen
2015-11-14 10:15 ` Marcin Borkowski
[not found] <mailman.2293.1447451126.7904.help-gnu-emacs@gnu.org>
2015-11-16 6:53 ` Dan Espen
2015-11-17 0:10 ` Emanuel Berg
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=871tbsbw01.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).