Gnus development mailing list
 help / color / mirror / Atom feed
From: Phillip Lord <phillip.lord@newcastle.ac.uk>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, bugs@gnus.org
Subject: Re: bug in recent version of nnml.el
Date: Fri, 03 Oct 2008 10:52:47 +0100	[thread overview]
Message-ID: <EMEW-k92Aqm3d49e454c5a1a9859976f63a24a05268-87ej2yqa34.fsf@dinley.ncl.ac.uk> (raw)
In-Reply-To: <EMEW-k920Zffc12dea83ee2ef6b314c1d218e22b9e9-b4m8wt6vadb.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri\, 03 Oct 2008 08\:35\:28 +0900")

>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:

  KY> Thank you for inquiring into the bug so closely.

No worries. It wanted to move my gnus emacs to 23 and this was stopping me, so
it was purely self-interest. 


  KY> Mail me if you've already signed or when you sign a paper to FSF.

Hmm. I have done this in the past, but I fear that they might be out of date. 
I don't know how to check this; any ideas? 

  KY> I've reverted those changes. Sorry. I realized it causes another error
  KY> if `nnmail-expiry-target' is the symbol `delete' that is the default. It
  KY> is not only a symbol but also a function symbol. I'll look for another
  KY> solution...


Unfortunate! Hadn't thought of that, of course. 

  KY> Fixed in the Gnus CVS trunk. The change I made in nnml.el is as follows.
  KY> Note that the function set to `nnmail-expiry-target' should be executed
  KY> in a buffer in which there is an article to be examined by the function
  KY> (your function might not care article contents, though).

Good stuff. My function just expires differently for different groups, so it
doesn't matter. In general, you are right though. This is what the
documentation says!

Phil



  parent reply	other threads:[~2008-10-03  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EMEW-k91AyF906d078456474eb10da550f3b4fb26ec-87od23724d.fsf@dinley.ncl.ac.uk>
2008-10-02 23:35 ` Katsumi Yamaoka
2008-10-02 23:50   ` Katsumi Yamaoka
2008-10-03  1:52     ` Katsumi Yamaoka
     [not found] ` <EMEW-k920Zffc12dea83ee2ef6b314c1d218e22b9e9-b4m8wt6vadb.fsf@jpl.org>
2008-10-03  9:52   ` Phillip Lord [this message]
2008-10-03 10:21     ` Katsumi Yamaoka
2008-10-03 14:48       ` Reiner Steib
     [not found]       ` <EMEW-k92Fmm5706e6efbf06ac13a4733671cc4e7a7c-87y715enuf.fsf@marauder.physik.uni-ulm.de>
2008-10-03 15:54         ` Phillip Lord
     [not found]     ` <EMEW-k92BM1c131f9b8dc92f8fae9342efde519d3d5-b4mwsgqhtc0.fsf@jpl.org>
2008-10-03 15:53       ` Phillip Lord

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=EMEW-k92Aqm3d49e454c5a1a9859976f63a24a05268-87ej2yqa34.fsf@dinley.ncl.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=bugs@gnus.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).