From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-mime-copy-part and saving
Date: Sat, 12 Apr 2003 22:57:22 +0200 [thread overview]
Message-ID: <m3brzbo2ml.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87vfxxhdyx.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> I'm contemplating the way gnus-mime-copy-part ("c" on a button) sets
> up the buffer it shows.
>
> With a random 8-bit application/octet-stream, like r.gz below, viewing
> with "c" and then attempting to save with C-x C-s prompts for a coding
> system, and it seems even no-conversion doesn't give the right bytes.
That's not unlikely -- showing binary stuff in Emacs is somewhat of
an ordeal these days...
> r.gz for instance should be 393 bytes, as revealled by an "o" save.
> And this is all of course with auto-compression-mode off so the zany
> jka-compr stuff doesn't get involved.
On the other hand, if you have jka-compr installed, `c' and `o' both
work perfectly. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-04-12 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 1:42 Kevin Ryde
2003-04-12 20:57 ` Lars Magne Ingebrigtsen [this message]
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=m3brzbo2ml.fsf@quimbies.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).