Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Marquardt <c.marquardt@alcatel.de>
Subject: [PATCH] gnus-group-clear-data in gnus.texi
Date: Wed, 09 Jan 2002 13:48:23 +0100	[thread overview]
Message-ID: <k8zofk34rmw.fsf@alcatel.de> (raw)

Hi,

since I got bitten by having renumbered articles suddenly, here is a
small patch for the docs.

I noted that gnus-cache-move-cache was not documented in gnus.texi at
all, so I added that too.

BTW, WIBNI there was a gnus-cache-move-cache-for-current-group or
something like that, to go with gnus-group-clear-data?



*** /tmp/gnus.texi.orig4843V8C	Wed Jan  9 13:44:43 2002
--- /tmp/gnus.texi4843iGJ	Wed Jan  9 13:44:43 2002
***************
*** 1357,1365 ****
--- 1357,1374 ----
  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,6813 ****
--- 6817,6826 ----
  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



             reply	other threads:[~2002-01-09 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09 12:48 Colin Marquardt [this message]
2002-01-10  0:50 ` 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=k8zofk34rmw.fsf@alcatel.de \
    --to=c.marquardt@alcatel.de \
    /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).