From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: doubly-gzipped files
Date: 18 Nov 1998 00:55:41 +0100 [thread overview]
Message-ID: <m3d86lub5u.fsf@sparky.gnus.org> (raw)
In-Reply-To: Alexandre Oliva's message of "16 Nov 1998 11:25:07 -0200"
Alexandre Oliva <oliva@dcc.unicamp.br> writes:
> jka-compr is enabled by default on my site. Whenever I save a gzipped
> attachment with the extension .gz, jka-compr will gzip it at save
> time, so I'll have to gunzip it twice to obtain the uncompressed
> contents. Is there any way GNUS could disable jka-compr (and any kind
> of translation, for that matter) for the buffer in which it saves
> files?
Hm. Good question. On the one hand, it should be possible to say
that the file should be saved to "something.gz" to signal that you
want "something" to be gzipped. But if the thing already has been
gzipped, and you just want to save it, that's not possible. So I
don't know how to work around this problem...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-17 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 13:25 Alexandre Oliva
1998-11-17 23:55 ` Lars Magne Ingebrigtsen [this message]
1998-11-18 15:38 ` Edward J. Sabol
1998-11-19 2:44 ` Lars Magne Ingebrigtsen
1998-11-20 4:40 ` Stephen Zander
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=m3d86lub5u.fsf@sparky.gnus.org \
--to=larsi@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).