Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Cc: ding@ifi.uio.no
Subject: Re: how do you subscribe to new groups if I don't save-killed
Date: 21 Feb 1996 14:49:10 -0500	[thread overview]
Message-ID: <ycq91hwwjbc.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 21 Feb 1996 00:05:51 +0100

>>>>> Lars Magne Ingebrigtsen writes:

> gsstark@MIT.EDU (Greg Stark) writes:

> Well, the "solution" is to set `gnus-read-active-file' to t.  This will make
> startup slower, though.

> One way or another, Gnus has to know what groups are available.  Either it
> must save the list of killed groups, or it must read the active file if you
> want to be able to do this sort of thing.

I currently have:
(setq gnus-read-active-file t)
(setq gnus-check-new-newsgroups '((nntp "news.mit.edu") (nnml "")))
(setq gnus-save-killed-list nil)

Commands like ``A m'' only list subscribed and unsuscribed groups.
No command seems to know about any killed groups.

greg


  parent reply	other threads:[~1996-02-21 19:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-02-20 14:58 Greg Stark
1996-02-20 23:05 ` Lars Magne Ingebrigtsen
1996-02-21 19:24   ` Patrick J. LoPresti
1996-02-21 20:42     ` Shane Holder
1996-02-21 21:11       ` Patrick J. LoPresti
1996-02-21 22:16         ` Shane Holder
1996-02-22  1:12     ` Lars Magne Ingebrigtsen
1996-02-21 19:49   ` Greg Stark [this message]
1996-02-22  6:01     ` Lars Magne Ingebrigtsen
1996-02-28  7:41       ` Greg Stark
1996-02-29  8:57         ` Lars Magne Ingebrigtsen
1996-02-29 15:59           ` Greg Stark
1996-03-01  9:04             ` Lars Magne Ingebrigtsen
1996-03-01 19:23               ` Greg Stark
1996-03-17 13:13                 ` Lars Magne Ingebrigtsen
1996-03-17 15:10                   ` Thomas Neumann
1996-03-19  3:34                   ` Greg Stark
1996-03-24  0:34                     ` Lars Magne Ingebrigtsen
1996-03-29  0:08                       ` Greg Stark
1996-03-29 16:11                         ` Lars Magne Ingebrigtsen

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=ycq91hwwjbc.fsf@fierce-bad-rabbit.MIT.EDU \
    --to=gsstark@mit.edu \
    --cc=ding@ifi.uio.no \
    /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).