From: Harry Putnam <reader@newsguy.com>
Subject: Re: Keeping up with what I download
Date: Sat, 11 Feb 2006 21:29:53 -0600 [thread overview]
Message-ID: <87ek29mez2.fsf@newsguy.com> (raw)
In-Reply-To: <200602111700.AA21037176@mail.ev1.net>
"Kevin Greiner" <kevin.greiner@compsol.cc> writes:
> You might consider adding %7F to your gnus-group-line-format. It
> is not quite not what you requested. However, it does tell you
> how much of your space is being used by each group on your local
> drive. I've found it quite useful when deciding where to do clean
> ups. The only disadvantage is that it scans your directories
> during start-up (it does do in-memory caching) so there is a
> performance penalty during start-up.
When I tried that I was unable to start gnus. I message buffer I see:
gnus-cache-update-file-total-fetched-for: Opening directory: no such
file or directory, /home/reader/News/cache/dummy.group
next prev parent reply other threads:[~2006-02-12 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 23:00 Kevin Greiner
2006-02-12 3:29 ` Harry Putnam [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-12 21:51 Kevin Greiner
2006-02-08 16:00 Harry Putnam
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=87ek29mez2.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).