Gnus development mailing list
 help / color / mirror / Atom feed
From: jhbrown@ai.mit.edu (Jeremy H. Brown)
Cc: Arnd Kohrs <kohrs@castify.net>,
	David Aspinwall <aspinwall@timesten.com>,
	ding@gnus.org
Subject: Re: spam*.el and ifile-gnus.el?
Date: 15 Sep 2002 14:16:10 -0400	[thread overview]
Message-ID: <uv6znujm845.fsf@suspiria.ai.mit.edu> (raw)
In-Reply-To: <vaf65xa3zli.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Maybe the right solution is to change gnus-request-*-article to run
> some hooks just before invoking the backend-specific functions.  Then
> your code can add stuff to the hooks.  WDYT?

That sounds perfect.  For full generality, you might even want hooks
before and after each of the backend-specific invocations.

Jeremy






  reply	other threads:[~2002-09-15 18:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 17:36 Kai Großjohann
2002-09-10 20:56 ` Alex Schroeder
2002-09-11  9:59   ` Kai Großjohann
2002-09-12  0:05     ` David Aspinwall
2002-09-12 15:35       ` Arnd Kohrs
2002-09-13  4:21         ` Jeremy H. Brown
2002-09-13  6:37           ` Andreas Fuchs
2002-09-13  7:17             ` Jeremy H. Brown
2002-09-13  7:50               ` Arnd Kohrs
2002-09-14  7:39                 ` Simon Josefsson
2002-09-15 18:16                 ` Jeremy H. Brown
2002-09-30 17:48                 ` Ted Zlatanov
2002-09-30 21:40                   ` Clemens Fischer
2002-09-13 11:20           ` Kai Großjohann
2002-09-15 18:16             ` Jeremy H. Brown [this message]
2002-09-13  3:39       ` Jeremy H. Brown
2002-09-30 17:54 ` Ted Zlatanov
2002-12-29 17:42   ` Lars Magne Ingebrigtsen
2002-12-29 19:06     ` Ted Zlatanov
2002-12-29 19:29       ` Lars Magne Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uv6znujm845.fsf@suspiria.ai.mit.edu \
    --to=jhbrown@ai.mit.edu \
    --cc=aspinwall@timesten.com \
    --cc=ding@gnus.org \
    --cc=kohrs@castify.net \
    /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.
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 NNTP newsgroup(s).