Re: Buttonizing and decoding based on message part contents?

[Lloyd Zusman <ljz@asfast.com>]

Jesper Harder <harder@ifa.au.dk> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Jesper Harder <harder@ifa.au.dk> writes:
>>
>>> [ ... ]
>>>
>>> Well, I don't actually know if `article-hide-pgp' did anything
>>> useful for multiparts.
>
> It does, at least for text/plain parts.  Try the attached patch.

Thank you.  I'll give it a try.


>> If there was a hook function that gets called for each message part
>> (and which allows me to set the display and buttonizing status for
>> each part), I could then write my own, personal code to handle this
>> case, and at the same time avoid polluting the Gnus code base with
>> this anachronism.
>
> The bad thing isn't pollution, but that the approach
> `article-hide-pgp' uses doesn't really solve the problems.  It just
> hides them, viz.
>
> · It doesn't allow you to actually verify the signatures.
> · It doesn't work for encrypted parts.
> · It doesn't necessarily (I haven't tested) solve the related problem
>   of format=flowed & old-style PGP.

OK.  That makes sense.

In addition to trying the patch that you have enclosed, I also still
want to try the "hook" idea that I mentioned above.  I'll see if I can
do this.

A question: if I write a washing-type function that traverses the MIME
structure of a message and calls a hook for each part, what should I do
within this hook in order to cause each of the following outcomes? ...

1. Buttonize the message part.

2. Override the part's MIME type with my own setting.  This will allow a
   text/plain or application/octet-stream part that contains delimiters
   such as "-----BEGIN PGP MESSAGE-----" to be handled via the code that
   already exists for application/pgp-encrypted parts.

Thanks.

-- 
 Lloyd Zusman
 ljz@asfast.com