unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Jenkins <brian@brianjenkins.org>
To: Bozhidar Batsov <bozhidar@batsov.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] frame.c: focus hooks
Date: Sun, 17 Nov 2013 17:25:33 -0500	[thread overview]
Message-ID: <CADTx1Ozm-j5en-Rsj=P7PsTYH5wnauhR1Z9bo4rSCZcRXskWwQ@mail.gmail.com> (raw)
In-Reply-To: <CAM9Zgm0UkiXDT5MZAOEe3pOGjz1E5Ae9ER-e95sVEA9VH=c6SA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

Thanks for the encouragement and feedback, Bozhidar.

I'm not married to the names.  I noticed that terms for focus gain/loss
seem to vary between platforms, so I used the event names used elsewhere in
the Emacs source.

Perhaps "focus-gain-hook" and "focus-loss-hook" would be more intuitive?

Brian


On Sun, Nov 17, 2013 at 1:29 PM, Bozhidar Batsov <bozhidar@batsov.com>wrote:

> I welcome your idea! In fact I've been thinking for quite some time we
> needed something like this. I don't like the names of the hooks, however,
> since they don't seem particularly standard - usually the terminology used
> with focus is "focus gained" and "focus lost" (or "on focus" and "on lose
> focus").
>
>
> On 17 November 2013 19:50, Brian Jenkins <brian@brianjenkins.org> wrote:
>
>> Hello.
>>
>> I'd like to contribute the attached patch, which adds hooks into gain and
>> loss of focus events.
>>
>> This allows saving all buffers on loss of focus.  (Alt-tabbing between
>> an editor and browser is a popular workflow for web programmers.)
>>
>> It also allows reversion of buffers on regain of focus, convenient if
>> one is switching between Emacs and another editor.
>>
>> People will probably find other handy uses for these hooks.
>>
>> Best,
>> Brian Jenkins
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2241 bytes --]

  reply	other threads:[~2013-11-17 22:25 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 [this message]
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
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='CADTx1Ozm-j5en-Rsj=P7PsTYH5wnauhR1Z9bo4rSCZcRXskWwQ@mail.gmail.com' \
    --to=brian@brianjenkins.org \
    --cc=bozhidar@batsov.com \
    --cc=emacs-devel@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 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).