From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Avoiding splitting of imap folders
Date: Mon, 23 Feb 2004 13:40:07 -0500 [thread overview]
Message-ID: <4nd685k5bs.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <vir4qtl7353.fsf@sunbroy2.informatik.tu-muenchen.de>
On Sat, 21 Feb 2004, skalberg@in.tum.de wrote:
> Hi Ted,
>
>>> (setq nnimap-split-inbox 'nil)
>>
>> I think you need (setq nnimap-split-inbox nil) there.
>>
>> I'm not sure if that's the only thing you need to do to eliminate
>> splitting, but that part above is definitely wrong; you're saying
>> "my nnimap split inbox is a symbol called 'nil', not nil itself".
>
> As far as I remember, nil just evaluates to itself, so 'nil and nil
> should be equivalent.
I see. I would stil use "nil" because it's less confusing, but sorry
for misleading you.
> In any case, my imap folder is still splitted when I follow your
> suggestion.
I looked at nnimap-split-articles in nnimap.el, and splitting is done
in nnimap-split-find-inbox using the value of nnimap-split-inbox,
whether that's a list or a single item (if a single item, it's
converted to a list). So just setting that to nil should do it!
It looks like setting the split rules to nil may also inhibit mail
splitting, but I don't understand why nnimap-split-inbox is not
respected. Try setting it to '() (an empty list):
(setq nnimap-split-inbox '())
and see if that helps. If not, try tracing through
nnimap-split-articles and see where it's getting "INBOX" from.
Ted
next parent reply other threads:[~2004-02-23 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vir1xopzus5.fsf@sunbroy2.informatik.tu-muenchen.de>
[not found] ` <4nbrntzgr1.fsf@collins.bwh.harvard.edu>
[not found] ` <vir4qtl7353.fsf@sunbroy2.informatik.tu-muenchen.de>
2004-02-23 18:40 ` Ted Zlatanov [this message]
[not found] ` <yoijk72dmitu.fsf@frealaf.dd.chalmers.se>
2004-02-24 16:53 ` Ted Zlatanov
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=4nd685k5bs.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.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).