Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@jhu.edu>
Subject: Re: Agent startup (how it works)
Date: Wed, 16 Jun 1999 10:30:33 -0500	[thread overview]
Message-ID: <87r9nckvs6.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Laura Conrad's message of "16 Jun 1999 10:26:21 -0400"

Laura Conrad <lconrad@concord.com> writes:
> Dan Christensen <jdc@jhu.edu> writes:
> > Robert Epprecht <epprecht@sunweb.ch> writes:
> > > ;; =========== .emacs
> > > (require 'gnus-agent)
> > 
> > > put (gnus-agentize) at the end of .gnus.el
> > 
> > It would be nice if both of these steps were unnecessary.  Is there
> > any reason that Gnus isn't always agentized?  Besides the "Plugged" in
> > the mode line, would a typical non-agent user even notice a
> > difference?
> 
> Your news postings and email would never get sent, if you didn't say
> "J S". 

Why not?  `M-x gnus' would start Gnus plugged.  And when plugged,
doesn't Gnus send mail and news immediately?

> That's actually one of the things I don't like about the design of the
> agent -- I don't think it should affect your mail at all unless you
> agentize the mail server.

When unplugged:

I think that Gnus should fetch incoming mail if the mail server isn't
agentized (and not fetch it if the mail server is agentized).  ("The"
mail server really means any mail server which has the get-new-mail
variable set.)

And similarly for incoming news.

For outgoing mail and news, I think the behaviour should be controlled
by a new variable.  For example, something like `gnus-agent-queue'
with possible values `t' (or `both'), `news', `mail' and `nil' (or `none').

Dan


  reply	other threads:[~1999-06-16 15:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3lnfpzejr.fsf@serpent.laymusic.>
1999-06-12  1:53 ` using the agent default category Lars Magne Ingebrigtsen
1999-06-14 18:05   ` Agent startup Robert Epprecht
1999-06-14 21:35     ` Kai.Grossjohann
1999-06-15 21:04       ` Agent startup (how it works) Robert Epprecht
1999-06-16  4:23         ` Dan Christensen
1999-06-16 14:26           ` Laura Conrad
1999-06-16 15:30             ` Dan Christensen [this message]
1999-06-17  1:03               ` Harry Putnam
1999-06-16 19:33             ` Kai.Grossjohann
1999-06-16 19:33               ` Laura Conrad
1999-07-03  9:05     ` Agent startup Lars Magne Ingebrigtsen
1999-07-04 10:51       ` Robert Epprecht
1999-07-05  3:53         ` Lars Magne Ingebrigtsen
1999-07-05 11:50           ` Robert Epprecht
1999-07-06  4:30             ` Lars Magne Ingebrigtsen
1999-07-06 21:57               ` Robert Epprecht
1999-07-09 16:59                 ` Lars Magne Ingebrigtsen

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=87r9nckvs6.fsf@chow.mat.jhu.edu \
    --to=jdc@jhu.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).