Gnus development mailing list
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: ding@gnus.org
Subject: ding and compression mode
Date: Sun, 30 Sep 2007 07:49:28 -0700	[thread overview]
Message-ID: <868x6ob43r.fsf@blue.stonehenge.com> (raw)


Back a few years ago, I was able to compress (using an external process)
my "fatter" nnml email, and setting

 '(auto-compression-mode t nil (jka-compr))

was enough to work properly.  The email stayed compressed until I visited the
actual file, and then it ballooned into the original size if I made any
changes, until the nightly process made it smaller again.  I'm a little fuzzy
on that last point... it might just have worked to recompress it.

However, some time in the recent releases (as in, in the past year or so),
this stopped working.  Visiting these emails showed up as a "file not found".
For now, I've uncompressed everything, but I'm wondering if anyone is aware of
a change that would have broken this for NNML.

I'm sorry I can't narrow it down to anything better than "recent release".  I
was too busy at the time to track it down.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!



             reply	other threads:[~2007-09-30 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 14:49 Randal L. Schwartz [this message]
2007-09-30 15:37 ` Reiner Steib
2007-09-30 17:10   ` Randal L. Schwartz

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=868x6ob43r.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --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).