From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mml-parse enhancement?
Date: 12 Jun 1999 07:04:03 +0200 [thread overview]
Message-ID: <m3vhcurovw.fsf@quimbies.gnus.org> (raw)
In-Reply-To: wmperry@aventail.com's message of "26 Apr 1999 11:43:39 -0500"
wmperry@aventail.com (William M. Perry) writes:
> Any chance I could convince everyone that mml-parse should return the
> marker positions of a native 'part'? Currently the 'contents' chunk of the
> assoc list contains the raw content.
>
> I'm diddling with getting a message-send-hook that is smart enough to use
> mailcrypt to sign the text/* parts with inlined content. Just for
> giggles. :)
>
> But because mml-parse returns the actual contents, I cannot use
> mc-sign-region very easily.
Well, I don't think just returning marker positions would solve the
problem completely. I mean, charsets are decoded and various other
funny stuff is done at various points in time. I actually think that
the way to sign stuff like that is to let MML generate MIME, and then
parse the MIME (`mm-dissect-buffer') and work based on that. Er. Or
something along those lines.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-06-12 5:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-26 16:43 William M. Perry
1999-06-12 5:04 ` 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=m3vhcurovw.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).