From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Richard Stallman <rms@gnu.org>
Cc: 15029@debbugs.gnu.org, dmol@gmx.com
Subject: bug#15029: 24.3; feature-request: add window-focus-lost-hook
Date: Thu, 08 Aug 2013 12:37:58 -0400 [thread overview]
Message-ID: <jwvob98qgy4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1V7SPn-0000KI-Sy@fencepost.gnu.org> (Richard Stallman's message of "Thu, 08 Aug 2013 11:46:15 -0400")
> We are talking about when the input focus enters and leaves Emacs in a
> GUI environment.
> It's the same kind of issue. I don't think Emacs should run any Lisp
> code when that happens -- it would make things hard to predict.
Following that same reasoning, we shouldn't have jit-lock.
And post-command-hook. And mouse-autoselect-window. And timers. Etc...
These all make debugging at times difficult.
Yes, these things should be used with care, but that doesn't mean we
shouldn't provide them, because they can be very useful.
Stefan
next prev parent reply other threads:[~2013-08-08 16:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 20:21 bug#15029: 24.3; feature-request: add window-focus-lost-hook Ivan Baidakou
2013-08-06 23:57 ` Glenn Morris
2013-08-07 19:21 ` Richard Stallman
2013-08-08 3:34 ` Glenn Morris
2013-08-08 15:46 ` Richard Stallman
2013-08-08 16:15 ` Glenn Morris
2013-08-09 2:38 ` Richard Stallman
2013-08-09 16:05 ` Glenn Morris
2013-08-09 23:23 ` Richard Stallman
2013-11-17 19:29 ` Glenn Morris
2013-11-19 2:24 ` Glenn Morris
2013-08-08 16:37 ` Stefan Monnier [this message]
2013-08-09 2:38 ` Richard Stallman
2013-08-09 7:42 ` Eli Zaretskii
2013-08-09 13:54 ` Stefan Monnier
2013-08-09 16:56 ` Richard Stallman
2013-08-09 17:43 ` Jan Djärv
2013-08-09 23:24 ` Richard Stallman
2013-08-09 18:40 ` Stefan Monnier
2013-08-08 16:56 ` Eli Zaretskii
2013-08-09 2:38 ` Richard Stallman
2013-08-09 7:37 ` Eli Zaretskii
2013-08-09 16:54 ` Richard Stallman
2013-08-09 18:20 ` Eli Zaretskii
2013-08-09 23:24 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvob98qgy4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=15029@debbugs.gnu.org \
--cc=dmol@gmx.com \
--cc=rms@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.