From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Lynbech Christian <christian.lynbech@tieto.com>
Cc: emacs-devel@gnu.org
Subject: Re: request: make-frame-visible hook
Date: Wed, 18 Feb 2009 11:54:16 -0500 [thread overview]
Message-ID: <jwvfxibwuue.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ytqptz6r7pu8.fsf@ul000240.eu.tieto.com> (Lynbech Christian's message of "Wed, 18 Feb 2009 15:59:59 +0100")
> Whether or not visibility tracking could be construed as useful, the
> problem still stands that there are multiple applications that wants to
> install stuff into special-event-map so perhaps a more generic solution
> should be sought such that multiple handlers can be present or registered
> for any event in that map?
We could easily setup a default handler that defers to a frame-local
make-frame-visible hook, indeed. But before doing that I think we'd
need to see what those things are used for. E.g. why does dframe mess
with the make-frame-visible events? What do you concretely do with
those events?
Stefan
next prev parent reply other threads:[~2009-02-18 16:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 20:14 request: make-frame-visible hook John J Foerch
2009-02-17 17:09 ` John J Foerch
2009-02-18 12:09 ` Richard M Stallman
2009-02-18 14:59 ` Lynbech Christian
2009-02-18 16:54 ` Stefan Monnier [this message]
2009-02-19 13:07 ` Lynbech Christian
2009-02-19 17:13 ` Stefan Monnier
2009-02-18 17:14 ` John J Foerch
2009-02-18 23:05 ` Richard M Stallman
2009-02-18 23:44 ` Stefan Monnier
2009-02-19 1:27 ` John J Foerch
2009-02-19 13:24 ` Lynbech Christian
2009-02-20 0:01 ` John J Foerch
2009-02-20 1:28 ` Miles Bader
2009-02-20 13:31 ` Richard M Stallman
2009-02-21 2:11 ` Kim F. Storm
2009-02-21 2:23 ` Stefan Monnier
2009-02-21 9:11 ` Eli Zaretskii
2009-02-21 14:10 ` martin rudalics
2009-02-21 17:41 ` Richard M Stallman
2009-02-21 20:59 ` Kim F. Storm
2009-02-22 3:31 ` Bo Lin
2009-02-22 14:35 ` Richard M Stallman
2009-02-21 20:43 ` Stefan Monnier
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=jwvfxibwuue.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=christian.lynbech@tieto.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).