Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: M-x gnus-no-server causes error in opening nnml folders
Date: Wed, 02 Apr 2008 11:27:40 +0900	[thread overview]
Message-ID: <b4mtzil56ub.fsf@jpl.org> (raw)
In-Reply-To: <u63v1zxf3.fsf@gmail.com>

>>>>> Sivaram Neelakantan wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> ,---- (info "(gnus)Group Levels") ----
>>| `S l'
>>|      Set the level of the current group.  If a numeric prefix is given,

> Well, that fixed it. But now I have the problem that it does try to
> access the mailserver when I set the level to 2.  Sometimes I just want
> offline access to the mailbox.  gnus-no-server was intuitive except
> for the frightening error. :) Really, for a minute I thought the nnml
> mail folder was a goner.

> At least, can there be a graceful "no" instead of an error like that?

Maybe `gnus-unplugged' is for you.

,---- (info "(gnus)Agent Basics") ----
| [...]
| * You start Gnus with `gnus-unplugged'.  This brings up the Gnus
|   Agent in a disconnected state.  You can read all the news that you
|   have already fetched while in this mode.
|
| * You then decide to see whether any new news has arrived.  You
|   connect your machine to the net (using PPP or whatever), and then
|   hit `J j' to make Gnus become "plugged" and use `g' to check for
|   new mail as usual.  To check for new mail in unplugged mode (*note
|   Mail Source Specifiers::).
| [...]
`----

I don't use it, but verified with a new temporary user account
that `gnus-unplugged' doesn't connect to the mail source.



      reply	other threads:[~2008-04-02  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31  7:37 Sivaram Neelakantan
2008-04-01  1:30 ` Katsumi Yamaoka
2008-04-01 10:23   ` Sivaram Neelakantan
2008-04-02  2:27     ` Katsumi Yamaoka [this message]

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=b4mtzil56ub.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).