unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John J Foerch <jjfoerch@earthlink.net>
To: emacs-devel@gnu.org
Subject: Re: request: make-frame-visible hook
Date: Thu, 19 Feb 2009 19:01:11 -0500	[thread overview]
Message-ID: <87mycit1rs.fsf@earthlink.net> (raw)
In-Reply-To: ytqphc2q4l1r.fsf@ul000205.eu.tieto.com

Lynbech Christian <christian.lynbech@tieto.com> writes:
> I do not know if you caught this, just want to make sure that you do,
> but as Stefan hinted you can fix the problem yourself. Just make sure
> dframe is loaded, overwrite the entry with your own function which runs
> a hook where you then stores anything that was in special-event-map
> before you put your own little function there.
>
> Alternatively you can consider using post-command-hook, this is run all
> the time and this particular problem should not pose a performance
> problem.


  Thank you for the ideas.  I am still hoping that at some point in the
future emacs will have a general solution to the problem, because
letting users and modes use special-event-map without conflicts and
hacks seems simple, logical, and useful.  (Why does special-event-map
exist if we can't use it safely?)  I can implement
make-frame-visible-hook in my .emacs, and require dframe, etc, and I
will do that if it is the only way, but unfortunately this prevents me
from submitting my improvement to tracking-mode or erc-track for others
to use.

  As a side-note, post-command-hook will not help in this situation
because tracking-mode already uses window-configuration-change-hook, but
the need to call an arbitrary command to force an update is precisely
what I am trying to avoid.

Thank you.

-- 
John Foerch





  reply	other threads:[~2009-02-20  0:01 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
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 [this message]
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=87mycit1rs.fsf@earthlink.net \
    --to=jjfoerch@earthlink.net \
    --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).