Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: agent and mail-source
Date: 01 Dec 1999 17:50:25 -0500	[thread overview]
Message-ID: <2n1z968edq.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "01 Dec 1999 19:36:35 +0100"

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>> But I am thinking to implement a parameter for mail-source, say
>> `:level'.  Level 1 is local, i.e. gnus will fetch the mail source
>> whenever it is plugged or not; level 3 (default) is remote, i.e. gnus
>> fetch the mail source only if it is plugged; level 6 is unactive
>> source, i.e. gnus does not fetch the mail unless in some special
>> cases.

LMI> Yes, this sounds like a good idea.  But isn't this really more of a
LMI> boolean thing?  If we're unplugged, we either do or don't want the
LMI> mail sources to kick in, so perhaps instead of :level we would have
LMI> something like :plugged that could have value nil or t?

>> For this reason, `:level' is a common parameter, i.e. each type of
>> mail source has this parameter. Therefore, put it in a common keywords
>> list variable, named `mail-source-common-keywords'.

LMI> Yup.

[...]

Done.

Now I use

(setq mail-sources 
        '((file :plugged t) 
          (webmail :subtype yahoo :user "shenghuo")))

Local mail is always checked, while Yahoo mail is checked only when
plugged.

-- 
Shenghuo


  reply	other threads:[~1999-12-01 22:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-19  7:07 Shenghuo ZHU
1999-12-01 18:36 ` Lars Magne Ingebrigtsen
1999-12-01 22:50   ` Shenghuo ZHU [this message]
     [not found]     ` <ur9h614pg.fsf_-_@TimesTen.com>
1999-12-02  3:46       ` webmail/yahoo problems Shenghuo ZHU

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=2n1z968edq.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).