From: Robert Pluim <rpluim@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: large *Gnus Backlog* buffer
Date: Wed, 22 Jul 2020 14:09:59 +0200 [thread overview]
Message-ID: <m2zh7rrbs8.fsf@gmail.com> (raw)
In-Reply-To: <874kpzpyvf.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 22 Jul 2020 12:34:12 +0100")
>>>>> On Wed, 22 Jul 2020 12:34:12 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:
Eric> Hello all,
Eric> I tend to start up emacs and keep it running, with gnus, for days if not
Eric> weeks. Today, I checked out Emacs's memory usage (M-x memory-usage RET)
Eric> and found that I have a ~ *Gnus Backlog*~ buffer that is >70MB in
Eric> size. Not a real worry on most of my systems but I'm curious:
Eric> 1. what function does this buffer have in gnus?
Eric> 2. can this be pruned back (manually or otherwise)?
I think this should help:
gnus-keep-backlog is a variable defined in `gnus.el'.
Its value is 20
You can customize this variable.
Probably introduced at or before Emacs version 19.32.
Documentation:
If non-nil, Gnus will keep read articles for later re-retrieval.
If it is a number N, then Gnus will only keep the last N articles
read. If it is neither nil nor a number, Gnus will keep all read
articles. This is not a good idea.
Thatʼs definitely a doc-string written by Lars :-)
Thereʼs also:
gnus-backlog-shutdown is an interactive compiled Lisp function in
`gnus-bcklg.el'.
(gnus-backlog-shutdown)
Clear all backlog variables and buffers.
Robert
next prev parent reply other threads:[~2020-07-22 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 11:34 Eric S Fraga
2020-07-22 12:09 ` Andreas Schwab
2020-07-22 12:09 ` Robert Pluim [this message]
2020-07-22 12:33 ` Eric S Fraga
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=m2zh7rrbs8.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).