unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Please try Pmail
Date: Wed, 21 Jan 2009 10:06:52 -0500	[thread overview]
Message-ID: <87zlhkitpv.fsf@cyd.mit.edu> (raw)
In-Reply-To: <jwv3afdpa6q.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 20 Jan 2009 23:18:10 -0500")

"Stefan Monnier" <monnier@iro.umontreal.ca> writes:

>> The annotation functions would need to add functions to that hook when
>> they are run.
>
> Not really.  When they switch to another buffer, they may need to adjust
> that hook in that buffer.  The default value could be `kill-buffer', so
> as to preserve current behavior.
>
>> Another idea: allow a new type of return value for annotation functions,
>> and use this to keep track of buffers to be killed.  For example, allow
>> annotation functions to return (FUN1 . FUN2), where FUN1 and FUN2 are
>> lambda functions.  Then FUN1 is called during annotation, and FUN2 is
>> called after other annotations have taken place.
>
> Since they return a buffer already, we may as well store the FUN2
> inside that buffer (as a buffer-local var).

They don't return a buffer.  They switch to a different buffer, and
return nil.

Here's one reason against adding a new hook to post-process annotations:
to do this particular job right, we need to run all the hook functions
in all the buffers that have been swapped to (so as to pick up their
local values).  This violates the usual behavior of run-hooks, which
only runs the buffer-local value of the hook, followed by the global
value of the hook.  The lambda function idea tries to avoid this by
making the post-processing part of the annotations process.




  reply	other threads:[~2009-01-21 15:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18  3:43 Please try Pmail Richard M Stallman
2009-01-18 14:47 ` Chong Yidong
2009-01-18 15:06   ` Alfred M. Szmidt
2009-01-18 20:40   ` Stefan Monnier
2009-01-19  1:41     ` Chong Yidong
2009-01-19  2:57     ` Chong Yidong
2009-01-20  4:57       ` Stefan Monnier
2009-01-20 14:20         ` Chong Yidong
2009-01-21  2:37           ` Stefan Monnier
2009-01-21  4:11             ` Chong Yidong
2009-01-21  4:18               ` Stefan Monnier
2009-01-21 15:06                 ` Chong Yidong [this message]
2009-01-21 20:38                   ` Stefan Monnier
2009-01-21 21:21                     ` Chong Yidong
2009-01-22  4:12                       ` Stefan Monnier
2009-01-22  4:55                         ` Chong Yidong
2009-01-23  1:52                           ` Richard M Stallman
2009-01-23  2:35                             ` Chong Yidong
2009-01-21 20:32               ` Richard M Stallman
2009-01-21 21:07                 ` Chong Yidong
2009-01-20 23:00         ` Richard M Stallman
2009-01-21  5:56           ` Eli Zaretskii
2009-01-20  1:00     ` Richard M Stallman
2009-01-19  4:31   ` Richard M Stallman
2009-01-19 14:39     ` Chong Yidong
2009-01-19  1:59 ` Glenn Morris
2009-01-20  0:59   ` Richard M 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=87zlhkitpv.fsf@cyd.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).