From f6c6f122181a3b9ce91b27bc635532cc3902614a Mon Sep 17 00:00:00 2001 From: Lars Magne Ingebrigtsen Date: Mon, 4 Jul 2011 01:32:31 +0200 Subject: [PATCH] (Checking New Groups): Moved the reference to the right place. --- texi/ChangeLog | 1 + texi/gnus.texi | 12 ++++++------ 2 files changed, 7 insertions(+), 6 deletions(-) diff --git a/texi/ChangeLog b/texi/ChangeLog index f8b16b2cc..de0f9dc4a 100644 --- a/texi/ChangeLog +++ b/texi/ChangeLog @@ -3,6 +3,7 @@ * gnus.texi (Subscription Methods): Link to "Group Levels" to explain zombies. (Checking New Groups): Ditto (bug#8974). + (Checking New Groups): Moved the reference to the right place. 2011-07-03 Dave Abrahams (tiny change) diff --git a/texi/gnus.texi b/texi/gnus.texi index ab2df31a1..f500a2ea6 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -1168,12 +1168,12 @@ when you do the @kbd{g} command (@pxref{Scanning New Messages}). @subsection Checking New Groups Gnus normally determines whether a group is new or not by comparing -the list of groups (@pxref{Group Levels}) from the active file(s) with -the lists of subscribed and dead groups. This isn't a particularly -fast method. If @code{gnus-check-new-newsgroups} is -@code{ask-server}, Gnus will ask the server for new groups since the -last time. This is both faster and cheaper. This also means that you -can get rid of the list of killed groups altogether, so you may set +the list of groups from the active file(s) with the lists of +subscribed and dead groups. This isn't a particularly fast method. +If @code{gnus-check-new-newsgroups} is @code{ask-server}, Gnus will +ask the server for new groups since the last time. This is both +faster and cheaper. This also means that you can get rid of the list +of killed groups (@pxref{Group Levels}) altogether, so you may set @code{gnus-save-killed-list} to @code{nil}, which will save time both at startup, at exit, and all over. Saves disk space, too. Why isn't this the default, then? Unfortunately, not all servers support this -- 2.25.1