Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kenneth Jacker <khj@be.cs.appstate.edu>
To: info-gnus-english@gnu.org
Subject: Changing Value of `gnus-use-cache'
Date: Tue, 01 Jul 2008 10:47:08 -0400	[thread overview]
Message-ID: <87skutr79v.fsf@be.cs.appstate.edu> (raw)

Out of ignorance, I have had `gnus-use-cache' set to `t' for a *long* time.

Rereading the documentation (info), indicates that a value of
`passive' would probably be better.  That value will only cache
articles that are "explicitly entered".

Some questions:

   If I change it to `passive', will the unnecessarily cached articles
   be automatically removed?  Or, must I do that myself.
   
   What does "explicitly entered" mean? ... only via the `!' and `?'
   commands?  What about `*'?

   Should I "tweak" the values of `gnus-cache-enter-articles' and/or
   `gnus-cache-remove-articles'?  Also, 'gnus-cacheable-groups'?
   
   Anything else I should watch out for if I make this change?


Reading the above leads me to realize that I probably should state
what I *want* to happen. ;-)

Basically, I want to avoid any unnecessary caching (I'm using `nnml'
"under my home directory"), and be able to retain ("forever")
newsgroup articles (others?) that are of interest.
   
Writing the above (and referring back to the documentation) has given
me some good ideas of how to change my configuration ... however, I'm
still interested in hearing from others.

Thanks!
-- 
Prof Kenneth H Jacker       khj@cs.appstate.edu
Computer Science Dept       www.cs.appstate.edu/~khj
Appalachian State Univ
Boone, NC  28608  USA        

                 reply	other threads:[~2008-07-01 14:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87skutr79v.fsf@be.cs.appstate.edu \
    --to=khj@be.cs.appstate.edu \
    --cc=info-gnus-english@gnu.org \
    --cc=khj@cs.appstate.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).