From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Do not want agantized, nnml backend.
Date: Mon, 26 Aug 2002 19:51:37 +0200 [thread overview]
Message-ID: <ilulm6tbj9y.fsf@latte.josefsson.org> (raw)
In-Reply-To: <20020826xjc3ct25php.kose@wizard.tamra.co.jp> =?iso-2022-jp?b?KBskQj4uNFgbKEIgGyRCNUhCJxsoQidz?= message of "Mon, 26 Aug 2002 11:21:38 +0900")
小関 吉則 (KOSEKI Yoshinori) <kose@meadowy.org> writes:
> But when Unplugged, In Summary buffer marked %. I can't read
> mails.
>
> Agentized backend is Only nntp and nnimap???
Amazing, I was about to add a patch that agentizes nntp and nnimap by
default, and it fixes your problem too.
I've committed my patch now, let me know if it doesn't work.
For everyone's information; GNUS-NEWS now says the following related
to the agent.
** gnus-agent
The Gnus Agent is now enabled by default. This means that, e.g.,
headers are not downloaded from agentized servers by default (agentize
servers by using `J a' in the server buffer). Gnus will not start to
download articles unless you instruct it to do so, though, by using
e.g. J u or J s from the group buffer. Revert to the old behaviour
with `(setq gnus-agent nil)'. Note that putting (gnus-agentize) in
~/.gnus is not needed any more. Now, by default all nntp and nnimap
servers from gnus-select-method and gnus-secondary-select-method are
agentized by default (earlier only the server in gnus-select-method
was agentized). You can view and change which servers should be
agentized in the Server Buffer.
next prev parent reply other threads:[~2002-08-26 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 2:21 小関 吉則
2002-08-26 17:51 ` Simon Josefsson [this message]
2002-08-26 22:49 ` Dan Christensen
2002-08-27 2:28 ` Harry Putnam
2002-08-27 10:30 ` Simon Josefsson
2002-08-27 10:26 ` Simon Josefsson
2002-08-27 16:47 ` Harry Putnam
2002-08-27 18:06 ` Simon Josefsson
2002-08-28 3:43 ` Harry Putnam
2002-08-30 1:26 ` Jesper Harder
2002-09-01 14:24 ` Simon Josefsson
2002-08-27 0:58 ` 小関 吉則
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=ilulm6tbj9y.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).