From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: [Patch] tell expiry-hook functions where expired messages are going
Date: Wed, 06 Aug 2014 16:45:57 +0800 [thread overview]
Message-ID: <871tsurooq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2sila82kw.fsf@polytechnique.org>
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> Hello,
>
> I gave this patch a try (as it's been applied to the git repo and I've
> been able to use it) and I'm seeing an error when messages are refiled
> during expiration.
Gah, that was my error. The patch should have used functionp and not
fboundp. Can someone fix that please?
Sorry!
E
> Here is the backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument symbolp "nnimap+zimbra:archive")
> fboundp("nnimap+zimbra:archive")
> gnus-summary-expire-articles()
> run-hooks(gnus-summary-prepare-exit-hook)
> apply(run-hooks gnus-summary-prepare-exit-hook)
> gnus-run-hooks(gnus-summary-prepare-exit-hook)
> gnus-summary-exit()
> call-interactively(gnus-summary-exit nil nil)
>
> The problematic string corresponds to the target mailbox for the
> expiration:
>
> #+begin_src emacs-lisp
> (setq gnus-parameters
> '(("^old.*"
> (total-expire . t)
> (expiry-wait . 1)
> (expiry-target . "nnimap+zimbra:archive"))
> ...
> ("^work$"
> (total-expire . t)
> (expiry-wait . 7)
> (expiry-target . "nnimap+zimbra:archive"))
> ...
> ))
>
> #+end_src
>
> Looking at the code, the error comes from the patched code. Shouldn't
> there be a check that `nnmail-expiry-target' is a symbol before calling
> fboundp?
>
> Thanks,
>
> Alan
next prev parent reply other threads:[~2014-08-06 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 9:04 Eric Abrahamsen
2014-08-06 8:06 ` Alan Schmitt
2014-08-06 8:45 ` Eric Abrahamsen [this message]
2014-08-06 11:00 ` Katsumi Yamaoka
2014-08-06 11:14 ` Katsumi Yamaoka
2014-08-06 16:22 ` Eric Abrahamsen
2014-08-11 14:07 ` Alan Schmitt
2014-08-14 7:42 ` Eric Abrahamsen
2014-08-14 11:30 ` Katsumi Yamaoka
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=871tsurooq.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).