From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: OK, so how do I *use* MIME?
Date: 13 Jan 1999 23:39:00 +0100 [thread overview]
Message-ID: <kiglnj6dchn.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "13 Jan 1999 19:33:04 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Hrvoje Niksic <hniksic@srce.hr> writes:
>
> > 1) It does allow me to view the article in the buffer, but saving it
> > or piping it to a command still saves the original junk, instead of
> > the decoded stuff. Is there a way to hook into the way *contents*
> > are handled, in order to allow easy saving of the junk?
>
> I don't think so. The CTE is decoded before saving/piping, but
> other than that, you deal with the untampered-with contents. Which
> seems logical to me -- when saving a GIF, one doesn't want it
> fiddled with before saving, for instance.
For GIF, I agree with you. But in this case, I would *like* to have a
hook to tamper with the contents at an early stage, similar to what
CTE processing does.
next prev parent reply other threads:[~1999-01-13 22:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 16:34 Hrvoje Niksic
1999-01-13 18:33 ` Lars Magne Ingebrigtsen
1999-01-13 22:39 ` Hrvoje Niksic [this message]
1999-01-13 23:26 ` Lars Magne Ingebrigtsen
1999-01-14 10:09 ` Kai.Grossjohann
1999-01-14 10:26 ` William M. Perry
1999-01-14 16:17 ` Hrvoje Niksic
1999-01-14 19:17 ` Lars Magne Ingebrigtsen
1999-01-14 23:29 ` Hrvoje Niksic
1999-01-15 0:17 ` Lars Magne Ingebrigtsen
1999-01-15 1:22 ` Hrvoje Niksic
1999-01-15 15:15 ` Lars Magne Ingebrigtsen
1999-01-15 2:29 ` lconrad
1999-01-15 15:16 ` Lars Magne Ingebrigtsen
1999-01-15 9:11 ` Steinar Bang
1999-01-15 15:16 ` Lars Magne Ingebrigtsen
1999-01-15 18:26 ` Graham Murray
1999-01-15 15:43 ` Andrew Hobson
1999-01-15 16:03 ` Lars Magne Ingebrigtsen
1999-01-14 0:36 ` William M. Perry
1999-01-14 15:36 ` Jari Aalto+list.ding
1999-01-14 16:01 ` William M. Perry
1999-01-14 16:11 ` Richard Coleman
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=kiglnj6dchn.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).