From: Bob Newell <bobnewell@bobnewell.net>
To: info-gnus-english@gnu.org
Subject: Re: Inhibiting gnus-get-new-news at startup, Re: Inhibiting gnus-get-new-news at startup, Re: Inhibiting gnus-get-new-news at startup
Date: Mon, 01 Jan 2024 16:35:25 -1000 [thread overview]
Message-ID: <815ejo7dpjuw.a8432vmrq@sc6g.hc3m175g6.info> (raw)
In-Reply-To: <87jzosk1ag.fsf@uwo.ca> (Dan Christensen's message of "Mon, 01 Jan 2024 19:48:55 -0500")
Dan Christensen <jdc@uwo.ca> writes:
> On Jan 1, 2024, James Thomas <jimjoe@gmx.net> wrote:
>
>> In addition to setting this to nil, I also set the levels ('S l' in the
>> Group buffer) of all the groups to 7 to achieve this.
>
> Level 7 is considered "unsubscribed", so that might cause some issues.
> Try level 3?
I've used this strategy for some years and level 5 works
perfectly for me. When I want to read a level 5 group, I
position to the group and M-1 g does it "on demand."
Only my INBOX is level 1 (I fetch from gmail).
--
Bob Newell
Honolulu, Hawai`i
- Via GNU-Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2024-01-02 2:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47073.0785092869$1703954497@news.gmane.org>
2023-12-30 19:01 ` Eric Abrahamsen
2023-12-31 3:38 ` Emanuel Berg
2023-12-31 23:27 ` Inhibiting gnus-get-new-news at startup, Re: Inhibiting gnus-get-new-news at startup, " James Thomas
2024-01-01 3:39 ` Eric Abrahamsen
2024-01-02 0:48 ` Dan Christensen
2024-01-02 2:35 ` Bob Newell [this message]
2024-01-03 3:34 ` Husain Alshehhi
[not found] ` <30352.9598562577$1704252905@news.gmane.org>
2024-01-03 12:09 ` Eric S Fraga
2024-01-03 15:23 ` Eric Abrahamsen
2024-01-03 16:06 ` Eric S Fraga
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=815ejo7dpjuw.a8432vmrq@sc6g.hc3m175g6.info \
--to=bobnewell@bobnewell.net \
--cc=info-gnus-english@gnu.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).