From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: nnmaildir oddities!
Date: Thu, 18 Jul 2002 16:16:40 -0400 [thread overview]
Message-ID: <87vg7c4wrb.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <m3lm887slu.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Sounds like a plan. Note that nnmaildir-get-new-mail is never
> defvar'ed (I don't feel safe setting it to t globally); it's only
> bound to t in a let form when nnmaildir calls nnmail-get-new-mail.
> I thought that was the only place where nnmaildir-get-new-mail would
> matter, but I could be wrong about that.
I think my head is about to explode trying to trace my way through the
nnmaildir code :) (no offense, I'm just not used to reading it...)
I *think* I may have found the problem, but I might be completely
missing it.
nnml-request-accept article uses nnmail-article-group when the group
is not passed in:
(if (stringp group)
(...)
(and
(nnmail-activate 'nnml)
(if (and (not (setq result (nnmail-article-group 'nnml-active-number)))
(yes-or-no-p "Moved to `junk' group; delete article? "))
(setq result 'junk)
(setq result (car (nnml-save-mail result))))
...
nnmail-article-group goes through the split methods to see what group
to save the article in.
In contrast, nnmaildir uses nnmaildir--prepare to generate a group if
one is not passed in, which just returns the current group:
(defun nnmaildir-request-accept-article (gname &optional server last)
(let ((group (nnmaildir--prepare server gname))
(coding-system-for-write nnheader-file-coding-system)
(buffer-file-coding-system nil)
(file-coding-system-alist nil)
srv-dir dir file tmpfile curfile 24h num article)
(catch 'return
(if group nil
(setf (nnmaildir--srv-error nnmaildir--cur-server)
(concat "No such group: " gname))
(throw 'return nil))
(setq gname (nnmaildir--grp-name group))
[...]
Am I off base here? If I'm reading this right (a big *if*), then
respooling with split rules doesn't work with nnmaildir -- it seems to
just re-save the article to the curent group!
This probably isn't the desired behavior...
Hopefully someone can explain this?
--
Josh Huber
next prev parent reply other threads:[~2002-07-18 20:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 16:34 Josh Huber
2002-07-18 17:08 ` Paul Jarc
2002-07-18 17:57 ` Josh Huber
2002-07-18 18:21 ` Paul Jarc
2002-07-18 18:41 ` Josh Huber
2002-07-18 19:17 ` Paul Jarc
2002-07-18 20:16 ` Josh Huber [this message]
2002-07-18 20:26 ` Paul Jarc
2002-07-18 20:42 ` Josh Huber
2002-07-18 20:59 ` Paul Jarc
2002-07-18 21:27 ` Josh Huber
2002-07-18 21:32 ` Paul Jarc
2002-07-19 7:23 ` Kai Großjohann
2002-07-19 19:34 ` Josh Huber
2002-07-26 19:32 ` Simon Josefsson
2002-07-26 20:06 ` Josh Huber
2002-07-26 20:33 ` Simon Josefsson
2002-07-26 20:44 ` Paul Jarc
2002-07-26 21:01 ` Josh Huber
2002-07-26 22:40 ` Simon Josefsson
2002-07-26 21:03 ` Simon Josefsson
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=87vg7c4wrb.fsf@mail.paradoxical.net \
--to=huber@alum.wpi.edu \
/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).