From: David S Goldberg <david.goldberg6@verizon.net>
Subject: Re: Agent forgets its servers
Date: Wed, 11 Dec 2002 15:39:59 -0500 [thread overview]
Message-ID: <u8zsmx4cmsg.fsf@blackbird-2k.MITRE.ORG> (raw)
In-Reply-To: <84hedk35dz.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Wed, 11 Dec 2002 17:08:24 +0100")
>>>>> On Wed, 11 Dec 2002 17:08:24 +0100, kai.grossjohann@uni-duisburg.de (Kai Großjohann) said:
> With the most recent change by Kevin, I see that Gnus forgets which
> servers are agentized. I'm sitting in the train and Gnus tried to
> connect to the servers. (I start "emacs -f kai-gnus-unplugged" when
> I log in which in turn executes gnus-unplugged.)
> So I thought, maybe it's a one-time-only thing and went to the server
> buffer and agentized all servers and closed them and exited Gnus.
> Then (in the same Emacs) I did M-x gnus-unplugged RET and Gnus had
> forgotten again that the servers were agentized.
> Maybe this is relevant:
> /----[ vdir ~/News/agent/lib ]
> | total 8
> | -rw-rw---- 1 kai kai 30 Nov 26 18:35 categories
> | -rw-rw---- 1 kai kai 84 Dec 11 16:56 servers
> \----
Well this explains the problem with gnus-agent-fetch-selected-article
however, I think the date on your servers file may be a red herring.
Mine did not change and the contents of the file look the way I think
I remember they should. It contains a list
("nnimap:server1" "nnimap:server2" nil)
Or should that be a more fully qualified server spec?
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2002-12-11 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 16:08 Kai Großjohann
2002-12-11 20:39 ` David S Goldberg [this message]
2002-12-12 11:38 ` Kai Großjohann
2002-12-12 11:40 ` Kai Großjohann
2002-12-13 13:10 ` Henrik Enberg
2002-12-14 6:36 ` Robert Epprecht
2002-12-14 7:04 ` kgreiner
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=u8zsmx4cmsg.fsf@blackbird-2k.MITRE.ORG \
--to=david.goldberg6@verizon.net \
/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).