From: Michael R. Wolf <MichaelRunningWolf@att.net>
Subject: Re: How to configure gnus 5.10.1 with group-split-fancy?
Date: Thu, 08 May 2003 14:47:51 -0700 [thread overview]
Message-ID: <u3cjp5cvs.fsf@att.net> (raw)
In-Reply-To: <uaddxnb4n.fsf@knight.6test.edu.cn>
Robin Hu <huxw@knight.6test.edu.cn> writes:
> Thanks Michael, it seems group-split-fancy cannot work with
> group-parameters, so I stick to nnmail-split-fancy now.
You're right. I had forgotten. I like the later because I'm already in
Gnus when I want to change parameters, so I do it from the Group menu.
For me, opening ~/.gnus and writing elisp wasn't the way to go. But it
did work for me for a while. That's why it was still laying around.
And it turns out that there are still some things I can do in the
~/.gnus file that I can't do from group-parameters.
Thanks for pointing this out for folks who may be lurking this
discussion, trying to make their own choice.
--
Michael R. Wolf
All mammals learn by playing!
MichaelRunningWolf@att.net
prev parent reply other threads:[~2003-05-08 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 16:15 Robin Hu
2003-05-07 19:46 ` Michael R. Wolf
2003-05-08 7:36 ` Robin Hu
2003-05-08 21:47 ` Michael R. Wolf [this message]
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=u3cjp5cvs.fsf@att.net \
--to=michaelrunningwolf@att.net \
/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).