Gnus development mailing list
 help / color / mirror / Atom feed
From: "Patrick J. LoPresti" <patl@eiffel.lcs.mit.edu>
Subject: Re: how do you subscribe to new groups if I don't save-killed
Date: Wed, 21 Feb 1996 14:24:02 -0500	[thread overview]
Message-ID: <199602211924.OAA01325@eiffel.lcs.mit.edu> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 21 Feb 1996 00:05:51 +0100

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "larsi" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

 larsi> gsstark@MIT.EDU (Greg Stark) writes:
 >> I'm not sure I understand what's going here, i think that if I
 >> have have: gnus-save-killed-list nil gnus-check-new-newsgroups
 >> 'ask-server
 >> 
 >> then Gnus doesn't know about any killed groups so when i use `j'
 >> or `U' it completes to just the groups I am subscribed to or are
 >> zombie groups.  I'm not sure the value of check-new-newsgroups is
 >> relevant, but I think save-killed-list is.

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

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

Perhaps there should be a way to ask Gnus to read the active file
explicitly?  The only time I need the active file read is when
subscribing to new groups, which isn't very often.

Thanks!

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMStxMHr7ES8bepftAQG+8AQAra8AwOy7mWv0L9yo0JmaEjjT7EvfBsLH
Wmt07Gx1icoNgnn6imwFXlA2vKxFthO/NkPfB7VEqfDRf5rhvQNFrdT6fiigJV9Y
xLJtyuwo50cn8RcH3zGogl72kLihCjX4VvHqMFwR0V1/TMDJm9FY1TjU7jUoIuKq
Ji1+dbyEgio=
=etyk
-----END PGP SIGNATURE-----


  reply	other threads:[~1996-02-21 19:24 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 [this message]
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
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=199602211924.OAA01325@eiffel.lcs.mit.edu \
    --to=patl@eiffel.lcs.mit.edu \
    --cc=patl@lcs.mit.edu \
    /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).