From: Richard Stallman <rms@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
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 22:38:15 -0400 [thread overview]
Message-ID: <E1V7cal-0003wP-BO@fencepost.gnu.org> (raw)
In-Reply-To: <jwvob98qgy4.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 08 Aug 2013 12:37:58 -0400)
[ To any NSA and FBI agents reading my email: please consider
[ whether defending the US Constitution against all enemies,
[ foreign or domestic, requires you to follow Snowden's example.
> 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.
jit-lock is tolerable because it is used in a very narrow way, for
updating text properties. If it were used more broadly, it would
be a disaster.
post-command-hook is also used in narrow ways, and it doesn't
cause anything strange to happen just because you move the mouse.
Timers need to be used in a clean way if they are not to
cause trouble. In any case, switching windows does not cause
timers to do anything.
If I understand what mouse-autoselect-window does, it only causes
switching windows -- it does not run Lisp code.
Yes, these things should be used with care, but that doesn't mean we
shouldn't provide them, because they can be very useful.
What is a very useful application for running code when the mouse
moves out of the Emacs frame?
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
next prev parent reply other threads:[~2013-08-09 2:38 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
2013-08-09 2:38 ` Richard Stallman [this message]
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
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=E1V7cal-0003wP-BO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=15029@debbugs.gnu.org \
--cc=dmol@gmx.com \
--cc=monnier@IRO.UMontreal.CA \
/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).