From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap does not create non-existent groups on expiry (lost mail)
Date: Wed, 08 Jan 2003 07:10:45 +0100 [thread overview]
Message-ID: <ilulm1wnpcq.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3heckff6d.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 08 Jan 2003 05:17:46 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> I think it is more appropriate in nnmail-expiry-target-group. What do
>> the nnmail experts say? Perhaps we can document this so it isn't a
>> problem in the future:
>>
>> Is nnfoo-request-accept-article supposed to create the group if it
>> does not exists, or is that up to the caller?
>
> It's up to the caller.
Then n-e-t-g should be fixed too?
2003-01-08 Simon Josefsson <jas@extundo.com>
* nnmail.el (nnmail-expiry-target-group): Request group, create it
not successful.
--- nnmail.el.~6.54.~ Sat Jan 4 00:13:49 2003
+++ nnmail.el Wed Jan 8 07:09:52 2003
@@ -1748,9 +1748,11 @@
(when (nnheader-functionp target)
(setq target (funcall target group)))
(unless (eq target 'delete)
+ (when (or (gnus-request-group target)
+ (gnus-request-create-group target))
(let ((group-art (gnus-request-accept-article target nil nil t)))
(when (consp group-art)
- (gnus-group-mark-article-read target (cdr group-art)))))))
+ (gnus-group-mark-article-read target (cdr group-art))))))))
(defun nnmail-fancy-expiry-target (group)
"Returns a target expiry group determined by `nnmail-fancy-expiry-targets'."
next prev parent reply other threads:[~2003-01-08 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 6:24 Nevin Kapur
2003-01-06 18:36 ` Nevin Kapur
2003-01-06 23:07 ` Simon Josefsson
2003-01-07 3:12 ` Nevin Kapur
2003-01-08 2:55 ` Simon Josefsson
2003-01-08 4:17 ` Lars Magne Ingebrigtsen
2003-01-08 6:10 ` Simon Josefsson [this message]
2003-01-08 6:40 ` Lars Magne Ingebrigtsen
2003-01-08 8:52 ` Simon Josefsson
2003-01-08 11:06 ` Nevin Kapur
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=ilulm1wnpcq.fsf@latte.josefsson.org \
--to=jas@extundo.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).