Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Add hooks to Gnus on move/edit/delete?
Date: Tue, 10 Sep 2002 22:04:14 +0200	[thread overview]
Message-ID: <vafelc1a9xd.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uv61y81vhe6.fsf@suspiria.ai.mit.edu> (jhbrown@ai.mit.edu's message of "10 Sep 2002 14:17:21 -0400")

jhbrown@ai.mit.edu (Jeremy H. Brown) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> I don't quite understand the meaning/purpose of the
>> nnmail-article-group advice, though.
>
> ifile-gnus is set up to do two things:
> - provide a recommendation to you to use during splits
> - record your actual decision, whether or not it was what ifile
>   recommended
>
> The nnmail-article-group advice works on both problems.
>
> First, it sticks the article buffer in the variable
> "ifile-article-buffer"; the ifile functions that you use in the split
> rely on this variable to hide the fact that, as discussed here
> recently, the actual name of the buffer varies depending on how the
> nnmail-article-group is entered (initial split or respooling or
> whatever).

Ah, so when Gnus is changed to record the buffer name in a variable,
then part of the need goes away.

> Second, after the split has been performed, the advice runs ifile
> record the actual split decision made.

And what to do about the other half?  What would be the right way to
remove the need for that half?

Are you willing to work on the proper integration of ifile into Gnus,
and would you sign the necessary papers for inclusion in Gnus?

kai

PS: It might be good to use message instead of print to provide
    debugging messages.
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)



  reply	other threads:[~2002-09-10 20:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 16:17 Kai Großjohann
2002-09-10 18:17 ` Jeremy H. Brown
2002-09-10 20:04   ` Kai Großjohann [this message]
2002-09-10 21:03     ` Jeremy H. Brown
2002-09-12 18:07       ` Clemens Fischer
2002-09-13  4:25         ` Jeremy H. Brown
2002-12-29 17:43 ` Lars Magne Ingebrigtsen
2002-12-29 18:34   ` Kai Großjohann
2002-12-29 18:44     ` Lars Magne Ingebrigtsen
2002-12-29 19:14     ` Ted Zlatanov
2002-12-29 22:06       ` Kai Großjohann
2002-12-29 22:53         ` Lars Magne Ingebrigtsen
2002-12-30  3:35           ` Ted Zlatanov
2002-12-30 18:49           ` Kai Großjohann
2002-12-30  3:33         ` Ted Zlatanov
2002-12-30 18:53           ` Kai Großjohann
2002-12-30 22:53             ` Ted Zlatanov
2002-12-31 12:08               ` Kai Großjohann
2002-12-31 14:32                 ` ifile-gnus: " Ted Zlatanov
2002-12-31 19:44                   ` Nathan J. Williams
2002-12-31 20:00                     ` Ted Zlatanov
2003-01-02 17:29         ` Simon Josefsson
2003-01-02 21:31           ` Kai Großjohann
2003-01-02 22:07             ` Simon Josefsson
2003-01-03 13:31               ` Kai Großjohann

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=vafelc1a9xd.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.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.
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).