From: Richard Riley <rileyrg@googlemail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: splitting working now : some issues/questions
Date: Sun, 10 Oct 2010 12:17:25 +0200 [thread overview]
Message-ID: <sopqvitkqy.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87eibyjuyq.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 10 Oct 2010 03:46:53 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sun, 10 Oct 2010 08:57:34 +0200 Richard Riley <rileyrg@googlemail.com> wrote:
>
> RR> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> On Sun, 10 Oct 2010 03:09:55 +0200 Richard Riley <rileyrg@googlemail.com>
> wrote:
>>>
> RR> Could (or should) the group parameter spam destination please default to
> RR> the groups server? Currently if I set the spam dest as an unqualified
> RR> Gnus-Spam for my nnimap server then its going to nnml:Gnus-Spam. I need
> RR> to currently fully qualify it to e.g nnimap+riley:Gnus-Spam.
>>>
>>> I think it should behave like a regular group name, which is the
>>> behaviour you're noting.
>
> RR> I am wondering why this would be better since unqualified is more
> RR> "local" and is the way for things like spam-split and spam-inbox. If
> RR> working on a group that belongs to a server it seems logical that merely
> RR> setting a group destination without fully qualifier such as
> RR> "nnimap+riles" means on that current group's server on not on some other
> RR> such as nnml which may, or may not, be random depending on select order.
>
> For spam-split and general splitting, actually I have wanted for a long
> time the group name to be qualified, but currently splitting only works
> to the same server. To keep with the Gnus conventions, I'd prefer to
> keep group names qualified whenever poassible.
>
> Ted
>
Yes, but why? If you are working a group in a certain server and
something operates on that server, unqualified makes a lot more sense
and is simply more convenient keeping in mind the manual talking about
not qualifying in other such settings. "spam" means "spam" folder on
this server, "nnml+otherserver:spam" means something else.
next prev parent reply other threads:[~2010-10-10 10:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 7:28 Richard Riley
2010-10-07 20:02 ` Lars Magne Ingebrigtsen
2010-10-08 14:46 ` Richard Riley
2010-10-08 17:30 ` Ted Zlatanov
2010-10-09 15:57 ` Lars Magne Ingebrigtsen
2010-10-10 0:38 ` Richard Riley
2010-10-10 1:09 ` Richard Riley
2010-10-10 6:13 ` Ted Zlatanov
2010-10-10 6:57 ` Richard Riley
2010-10-10 8:46 ` Ted Zlatanov
2010-10-10 10:17 ` Richard Riley [this message]
2010-10-10 13:38 ` Andreas Schwab
2010-10-10 14:35 ` Richard Riley
2010-10-10 15:04 ` Ted Zlatanov
2010-10-10 16:28 ` Richard Riley
2010-10-11 13:37 ` Ted Zlatanov
2010-10-11 13:55 ` Richard Riley
2010-10-10 7:27 ` Richard Riley
2010-10-10 11:10 ` Richard Riley
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=sopqvitkqy.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
--cc=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).