From 070368696961c8b5128278a4b05140d7691c2a5e Mon Sep 17 00:00:00 2001 From: Lars Magne Ingebrigtsen Date: Thu, 10 Jan 2002 00:54:41 +0000 Subject: [PATCH] 2002-01-10 Colin Marquardt * gnus.texi (Changing Servers): Addition. --- texi/ChangeLog | 4 ++++ texi/gnus.texi | 13 +++++++++++++ 2 files changed, 17 insertions(+) diff --git a/texi/ChangeLog b/texi/ChangeLog index 19c96ec49..45bc03f82 100644 --- a/texi/ChangeLog +++ b/texi/ChangeLog @@ -1,3 +1,7 @@ +2002-01-10 Colin Marquardt + + * gnus.texi (Changing Servers): Addition. + 2002-01-06 ShengHuo ZHU * gnus.texi (Archived Messages): Rename diff --git a/texi/gnus.texi b/texi/gnus.texi index 5b04633db..a56504a7a 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -1357,9 +1357,18 @@ and read ranges have become worthless. You can use the @kbd{M-x gnus-group-clear-data-on-native-groups} command to clear out all data that you have on your native groups. Use with caution. +@kindex M-x gnus-group-clear-data +@findex gnus-group-clear-data +Clear the data from the current group only---nix out marks and the +list of read articles (@code{gnus-group-clear-data}). + After changing servers, you @strong{must} move the cache hierarchy away, since the cached articles will have wrong article numbers, which will affect which articles Gnus thinks are read. +@code{gnus-group-clear-data-on-native-groups} will ask you if you want +to have it done automatically; for @code{gnus-group-clear-data}, you +can use @kbd{M-x gnus-cache-move-cache} (but beware, it will move the +cache for all groups). @node Startup Files @@ -6808,6 +6817,10 @@ gnus-cache-generate-nov-databases} will (re)build all the @sc{nov} files, and @kbd{gnus-cache-generate-active} will (re)generate the active file. +@findex gnus-cache-move-cache +@code{gnus-cache-move-cache} will move your whole +@code{gnus-cache-directory} to some other location. You get asked to +where, isn't that cool? @node Persistent Articles @section Persistent Articles -- 2.25.1