Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: splitting docs
Date: Mon, 24 Jan 2011 16:37:24 -0600	[thread overview]
Message-ID: <87d3nm6i8r.fsf@lifelogs.com> (raw)
In-Reply-To: <871v42osy7.fsf@gnus.org>

On Mon, 24 Jan 2011 14:08:48 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Yeah, that's the problem.  I think you (or I) should write a "split
>> methods verifier" that tells you, given your current configuration, what
>> Gnus will do when splittin' time comes.

LI> Heh.  I think that's quite difficult.  The variables will be used as
LI> defaults for the slots (sort of), but you won't be able to see easily
LI> whether a different set of values will eventually be substituted once
LI> the select method has been "activated".  I mean, in case you have more
LI> than one nnimap backend.

Maybe then talk more at splittin' time, explaining "I found this info in
the split slot, and it's fancy, and like my cousin is single and totally
into you so she asked for your number, and oh here's a spam message..."

Ted




  reply	other threads:[~2011-01-24 22:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 14:45 Richard Riley
2010-12-19 15:34 ` Andreas Schwab
2010-12-19 16:04   ` Richard Riley
2010-12-20 17:18 ` Lars Magne Ingebrigtsen
2010-12-20 17:56   ` Richard Riley
2010-12-20 17:57     ` Lars Magne Ingebrigtsen
2011-01-19 22:17       ` Ted Zlatanov
2011-01-22  3:04         ` Lars Ingebrigtsen
2011-01-24 17:58           ` Ted Zlatanov
2011-01-24 22:08             ` Lars Ingebrigtsen
2011-01-24 22:37               ` Ted Zlatanov [this message]
2011-01-24 23:28                 ` Lars Ingebrigtsen
2011-01-25 17:00                   ` Ted Zlatanov
2011-01-25 22:09                     ` Lars Ingebrigtsen
2011-01-26 16:59                       ` 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=87d3nm6i8r.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).