From: Daniel Dehennin <daniel.dehennin@baby-gnu.org>
To: ding@gnus.org
Subject: Re: [PATCH] Fontification of an org-mode source block in PGP signed message does not work
Date: Fri, 29 Jul 2011 11:43:58 +0200 [thread overview]
Message-ID: <8762mlmnfl.fsf@hati.baby-gnu.org> (raw)
In-Reply-To: <sa31ux94gmm.fsf@cigue.easter-eggs.fr>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
Julien Danjou <julien@danjou.info> writes:
> On Thu, Jul 28 2011, Daniel Dehennin wrote:
>
>> The problem is located in 'mm-dissect-buffer' which does not define the
>> content-disposition if none is present in the MIME header.
>
> Good one.
>
> I've simplified it a bit, I hope I did not break it. At least it seems
> to work for me. :)
It works, I switched to string-match to parse other mm-inline-text-*
without Content-Disposition header, I found only two others:
- mm-inline-text-html
- mm-inline-text-vcard
So, just mm-inline-text is sufficient.
Thanks.
--
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2011-07-29 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 17:44 Daniel Dehennin
2011-07-29 8:48 ` Julien Danjou
2011-07-29 9:43 ` Daniel Dehennin [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=8762mlmnfl.fsf@hati.baby-gnu.org \
--to=daniel.dehennin@baby-gnu.org \
--cc=ding@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).