Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: #pranav@cisco.com (Pranav K. Tiwari)
Subject: Re: expiry-target
Date: Wed, 13 Aug 2003 12:04:13 +0530	[thread overview]
Message-ID: <u65l2t6ai.fsf@cisco.com> (raw)
In-Reply-To: <ilu65l2rdgz.fsf@latte.josefsson.org>

>
>> Found a diff in my CVS tree which I think could be useful to others too.
>>
>> There are two places where nnmail-expiry-target is used. On gnus-group.el,
>> it's run through format-time-string, but in gnus-sum.el, it's not. The
>> following diffs fix the discrepancy.
>>
>> -p
>>
>>
>> Index: gnus-sum.el
>> ===================================================================
>> RCS file: /usr/local/cvsroot/gnus/lisp/gnus-sum.el,v
>> retrieving revision 6.356
>> diff -r6.356 gnus-sum.el
>> 9192a9193,9196
>>> 	   (nnmail-expiry-target
>>> 	    (if (stringp nnmail-expiry-target)
>>> 		(format-time-string nnmail-expiry-target)
>>> 	      nnmail-expiry-target))
>
> In my gnus, format-time-string is not invoked on *-expiry-target in
> neither file?

Sorry - my bad ..

Looked more carefully, and realized that format-time-string was added into
both files by me in my local CVS tree. I remember I was looking for the
ability to archive expired mails from different months into different
folders, and using a function as expiry-target didn't work very well on
nnimap groups. So, I had hacked this code to run format-time-string to
achieve that purpose.

-p


       reply	other threads:[~2003-08-13  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <u8ypzvuof.fsf@cisco.com>
     [not found] ` <ilu65l2rdgz.fsf@latte.josefsson.org>
2003-08-13  6:34   ` Pranav K. Tiwari [this message]
2002-08-15 13:02 expiry-target Mike Woolley

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=u65l2t6ai.fsf@cisco.com \
    --to=#pranav@cisco.com \
    /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).