From: Justin Sheehy <dworkin@ccs.neu.edu>
Subject: my inattentiveness, and agent/imap
Date: 02 May 2000 19:01:31 -0400 [thread overview]
Message-ID: <vndn1m8d0ac.fsf@camelot-new.ccs.neu.edu> (raw)
I've been very busy of late due to a new job and some other
changes, and thus have not been reading ding and g.e.g quite as
thoroughly as I used to. If something comes up that merits a change
to the FAQ and I don't do anything about it, feel free to send me
email alerting me to that.
And now for something completely different...
I finally am in a situation where the combination of nnimap and
nnagent is useful (actually, pretty much necessary) for me. It seems
to be almost working, yet I apparently missed something.
I added (gnus-agentize) to the end of my .gnus.el and added my nnimap
server to the agent with `J a'. I can do things when plugged such as
`J s', which seems to succeed at transferring articles. However, when
I start Gnus unplugged, all of my groups are *'ed out. If I try to do
a M-g on a group while unplugged, I get:
<group name here> error: Invalid group (no such directory)
Thus, unpluggedness isn't too useful.
Also, the next time that I start Gnus plugged after going unplugged,
all groups are *'ed out. M-g on a group in this state does succeed in
scanning the group and making it live.
I must be missing something simple in my agent setup. Any ideas?
-Justin
next reply other threads:[~2000-05-02 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 23:01 Justin Sheehy [this message]
2000-05-02 23:39 ` Justin Sheehy
2000-05-04 15:52 ` Steinar Bang
2000-05-04 20:09 ` Justin Sheehy
2000-05-04 21:17 ` Steinar Bang
2000-05-05 0:59 ` agent/imap Justin Sheehy
2000-05-05 9:41 ` agent/imap Steinar Bang
2000-05-09 18:58 ` agent/imap Justin Sheehy
2000-05-10 7:22 ` agent/imap Kai Großjohann
2000-05-10 21:53 ` agent/imap Justin Sheehy
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=vndn1m8d0ac.fsf@camelot-new.ccs.neu.edu \
--to=dworkin@ccs.neu.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).