From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23374 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: Agent startup (how it works) Date: 16 Jun 1999 18:03:30 -0700 Sender: owner-ding@hpc.uh.edu Message-ID: References: <"m3lnfpzejr.fsf"@serpent.laymusic> <87aeu0pyck.fsf@chow.mat.jhu.edu> <87r9nckvs6.fsf@chow.mat.jhu.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035161118 1645 80.91.224.250 (21 Oct 2002 00:45:18 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:45:18 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id VAA08959 for ; Wed, 16 Jun 1999 21:07:39 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id UAB02856; Wed, 16 Jun 1999 20:04:01 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 16 Jun 1999 20:04:49 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id UAA20977 for ; Wed, 16 Jun 1999 20:04:39 -0500 (CDT) Original-Received: from mail.networkone.net (qmailr@mail.networkone.net [209.144.112.75]) by sclp3.sclp.com (8.8.5/8.8.5) with SMTP id VAA08829 for ; Wed, 16 Jun 1999 21:03:41 -0400 (EDT) Original-Received: (qmail 30624 invoked from network); 17 Jun 1999 01:05:10 -0000 Original-Received: from pm3-3-13.la.networkone.net (HELO satellite.local.lan) (reader@209.144.126.141) by mail.networkone.net with SMTP; 17 Jun 1999 01:05:10 -0000 Original-Received: (from reader@localhost) by satellite.local.lan (8.9.1/8.9.1) id SAA00954; Wed, 16 Jun 1999 18:03:30 -0700 Original-To: ding@gnus.org In-Reply-To: Dan Christensen's message of "Wed, 16 Jun 1999 10:30:33 -0500" Original-Lines: 73 User-Agent: Gnus/5.070083 (Pterodactyl Gnus v0.83) Emacs/20.3 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:23374 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:23374 Dan Christensen writes: > Laura Conrad writes: > > Dan Christensen writes: > > > Robert Epprecht 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. Agent already does this for incoming news ( on unagentized servers) > 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'). This might be a possible course, but my own feeling is that when "unplugged", gnus should behave as if actually unplugged, that is, no racing on-line if you happen to press on a group belonging to an unagentized server (nntp). Currently the behavior is mixed and confusing. At present , no mail can be gotten when unplugged, yet news in unagentized nntp groups can. But try to send a message while in that group and it isn't sent but queued, even though you are actually on-line yet unplugged. I think it would be lots less confusing if the behavior was consistent across all groups. When unplugged, no plugged type activity. Anything that gnus can access on the local machine, should be possible while unplugged or plugged. Mail on the local spool should be able to be incorporated. Same for any News spool on the local machine. If it doens't require going online then gnus should be able to do it "unplugged". The "can't do that while unplugged" message you get when pressing `J s' should have a concomitant message that comes up when pressing `C-c C-c' while unplugged, telling you that you have queued a message and not "sent" it. Don't know how others do, but I often forget to send them. Or forget that I am unplugged, close gnus, later wondering why my message isn't showing up. Then later still, when batching, I see something being sent and wonder what the heck it was. That mode line message just isn't making it for me. Of course, that may just be early onset senility....