From: Peter Rooney <pt@panix.com>
Subject: Re: splitting based on charset
Date: 23 Jul 2002 13:22:02 -0400 [thread overview]
Message-ID: <mxrn0sigy11.fsf@panix1.panix.com> (raw)
In-Reply-To: <wurw8odq.fsf@bitstream.com>
Peter Davis <pd@world.std.com> writes:
> I catch most of these with ...
>
> (setq nnmail-split-methods 'nnmail-split-fancy)
> (setq nnmail-split-fancy
> '(| ("Content-Type" "ks_c_5601-1987" "spam")
> ("Content-Type" "euc-kr" "spam")
> .
> .
> .
> ))
can someone help me integrate this approach with my mail splitting
set-up, which relies completely on group parameters? i use
to-address, from-address, extra-aliases, etc. to split my mail into
mail groups; i can't quite figure out how to get the charset splitting
(like the above) into the mix. rooting around in the docs and using
describe-function seem to suggest that gnus-group-split-fancy is the
function that's actually doing my splitting, but my lame elisp
attempt:
(setq gnus-group-split-fancy
(cons (gnus-group-split-fancy)
'(| ("Content-Type" "ks_c_5601-1987" "spam")
("Content-Type" "euc-kr" "spam"))))
does not seem to get the charset splitting into the function
split definition.
tia,
peter
http://www.fodny.com
parent reply other threads:[~2002-07-23 17:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <wurw8odq.fsf@bitstream.com>]
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=mxrn0sigy11.fsf@panix1.panix.com \
--to=pt@panix.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).