Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: How to not check for new messages at start-up?
Date: Tue, 18 Oct 2011 09:09:31 +0100	[thread overview]
Message-ID: <87ipnmyb44.fsf@ucl.ac.uk> (raw)
In-Reply-To: <877h42u9oq.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 18 Oct 2011 13:53:57 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> On Tue, Oct 18 2011, Teemu Likonen wrote:
>
>> When Gnus is started it automatically checks for new messages. Can I
>> prevent that? Sometimes I don't want this automatic "g" command but just
>> a quick M-g on a specific group.
>
> If you use `gnus-unplugged' instead of `gnus', that should do what you
> want. You might have to be using the agent, and it doesn't always
> behave exactly as you'd expect, but that's the basic idea…
>
> Eric

or set gnus-activate-level to a very low number:

,----[ C-h v gnus-activate-level RET ]
| gnus-activate-level is a variable defined in `gnus-start.el'.
| Its value is 2
| Original value was 6
| 
| Documentation:
| *Groups higher than this level won't be activated on startup.
| Setting this variable to something low might save lots of time when
| you have many groups that you aren't interested in.
| 
| You can customize this variable.
| 
| [back]
`----

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 + No Gnus v0.18



       reply	other threads:[~2011-10-18  8:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fwircqc5.fsf@imladris.arda>
     [not found] ` <877h42u9oq.fsf@ericabrahamsen.net>
2011-10-18  8:09   ` Eric S Fraga [this message]
2011-10-18  9:52     ` Eric Abrahamsen
2011-10-18 10:17       ` Eric Abrahamsen
2011-10-18 16:53         ` Eric S Fraga
2011-10-19  0:58           ` Eric Abrahamsen

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=87ipnmyb44.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).