From: Norman Walsh <ndw@nwalsh.com>
Subject: Re: split-fancy problem...
Date: Mon, 6 Sep 1999 13:58:38 -0400 [thread overview]
Message-ID: <9467-Mon06Sep1999135838-0400-ndw@nwalsh.com> (raw)
In-Reply-To: Robert Bihlmeyer's message of "06 Sep 1999 12:33:07 +0200"
| Because of that, `(any "LETPRESS@" "letterpress")' will not fire, so
| this message will end up in your catch-all group - "spam".
Thanks, Robert, that gets me closer. Ok, I've changed all the lines
that read
(any "something@" "something")
to
(any "something@.*" "something")
and that seems to work much better. The splits seem to be working.
But, there's still one problem...
I'm using the leading (& split to make archival copies of all my
messages in
nnml:archive.1999-09
But after the split runs, that group doesn't seem to reflect the new
contents until I exit gnus and restart. Do I have to do something else
to get the active/overview file to update?
Similarly, now that I've got a single archive group for all the incoming
mail, I'd like to make all my outgoing mail archive there as well,
so I set
(setq gnus-message-archive-group
'((if (message-news-p)
"news"
(concat "nnml:" (nwalsh-incoming-group)))))
(Where (nwalsh-incoming-group) returns "archive.yyyy-mm")
Again, after sending a new message, I can see that it's been deposited
in the right directory, but gnus doesn't know about it until I exit
and restart.
Cheers,
norm
--
Norman Walsh <ndw@nwalsh.com> | Nature is amoral, not immoral.
http://nwalsh.com/ | [It] existed for eons before we
| arrived, didn't know we were
| coming, and doesn't give a damn
| about us.--Stephen J. Gould
next prev parent reply other threads:[~1999-09-06 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-04 20:47 Norman Walsh
1999-09-06 10:33 ` Robert Bihlmeyer
1999-09-06 17:58 ` Norman Walsh [this message]
1999-09-07 7:45 ` Robert Bihlmeyer
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=9467-Mon06Sep1999135838-0400-ndw@nwalsh.com \
--to=ndw@nwalsh.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).