Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: viewing attachments
Date: Fri, 11 Feb 2005 10:43:33 +1100	[thread overview]
Message-ID: <87is50vv4q.fsf@zip.com.au> (raw)
In-Reply-To: <b9y3bw4vghk.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
> Done.

On a foo.gz attachment, with auto-compression-mode disabled, using
copy-part to get a buffer and then saving that buffer produces a file
different from the original.

I think this didn't work before either, but I think it prompted for a
coding system before, which is always a good clue that something evil
is happening and you're likely to get garbage.

Personally I only ever save stuff with "o", but it'd be nice if
copy-part could work too.



  reply	other threads:[~2005-02-10 23:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 10:38 Katsumi Yamaoka
2005-02-07 23:05 ` Kevin Ryde
2005-02-09  2:41   ` Katsumi Yamaoka
2005-02-09  8:19     ` Katsumi Yamaoka
2005-02-10 10:47       ` Katsumi Yamaoka
2005-02-10 23:43         ` Kevin Ryde [this message]
2005-02-11  4:00           ` Katsumi Yamaoka
2005-02-12  2:11             ` Katsumi Yamaoka

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=87is50vv4q.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).