From: storm@cua.dk (Kim F. Storm)
To: rms@gnu.org
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: request: make-frame-visible hook
Date: Sat, 21 Feb 2009 21:59:37 +0100 [thread overview]
Message-ID: <87tz6nwlom.fsf@kfs-lx.rd.rdm> (raw)
In-Reply-To: <E1Lavqh-0002Ml-Ln@fencepost.gnu.org> (Richard M. Stallman's message of "Sat, 21 Feb 2009 12:41:11 -0500")
Richard M Stallman <rms@gnu.org> writes:
> before-modify-buffer-hook (run before changing buffer)
> after-modify-buffer-hook (run after changing buffer)
>
> Modification hooks already do exist.
> Are they somehow inadequate?
Can't remember offhand - maybe.
>
> before-cursor-move-hook
> after-cursor-move-hook
>
> Text properties exist to do this.
> Are they somehow inadequate?
It is not appropriate for "global modes" to add text properties
everywhere - that's even worse than using post-command-hook IMO.
>
> before-window-buffer-change-hook
> after-window-buffer-change-hook
> focus-window-hook
> unfocus-window-hook
> enter-buffer-hook
> exit-buffer-hook
>
> What packages would want these, and what are they trying to do?
I cannot say for sure.
I have had various ideas over the years, but did not pursue them
of lack of a simple way to hook this into existing framework.
One example I recall is to properly restore window buffers
after displaying the *Help* buffer - the current "suggested
restore previous buffer command" falls flat on its face if
you have two windows showing different portions of the same buffer -
and one of the windows is taken by the *Help* buffer.
Focus/unfocus window would be used to change the background
color of active/inactive window.
enter-buffer / exit-buffer I know I needed at some point, but
I don't recall right now.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2009-02-21 20:59 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
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 [this message]
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=87tz6nwlom.fsf@kfs-lx.rd.rdm \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--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 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).