From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: could a large (2.4Mb) .newsrc.eld file slow things down
Date: Fri, 28 Jan 2022 22:03:47 +0100 [thread overview]
Message-ID: <87leyzo9n0.fsf@mat.ucm.es> (raw)
In-Reply-To: <875yq3rabu.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:
> You could try to compact the article number lists, especially the seen
> list can have a lot of holes. You can do that with G E
> (gnus-group-edit-group) from the *Group* buffer.
I just tried that command out: what do you mean by compact? Delete lines that look not worth to be kept?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-01-28 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 15:30 Uwe Brauer
2022-01-28 15:58 ` Tassilo Horn
2022-01-28 17:08 ` Uwe Brauer
2022-01-28 17:19 ` Eric Abrahamsen
2022-01-31 13:22 ` Eric S Fraga
2022-01-28 18:20 ` Andreas Schwab
2022-01-28 21:03 ` Uwe Brauer [this message]
2022-01-28 21:35 ` Andreas Schwab
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=87leyzo9n0.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/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).