VM-BUG: vm-followup-include-text parses multipart message wrong

[Stephen J. Turnbull]

Julian Bradfield writes:
 > stephen writes:

 > >MIME isn't relevant here; it's a wire protocol.  What the MUA *does*
 > >is up to the MUA, MIME just tells it how to interpret what it gets off
 > >the wire.
 > 
 > Technically, yes - but realistically don't most MUAs use the structure
 > described by MIME to structure their messages?

When they go back on the wire, of course.  However, in the MUAs I use
alone there are two different non-MIME methods: VM uses an elegant
extent-as-button-with-properties to specify it while Gnus uses a grody
*ML-ish mishmash.

However, the interpretation I had in mind was to flatten all the text
parts into a single quoted slab of text.  This violates the MIME
structure, of course, and that's what I mean by "the MUA can do what
it wants to".

 > What it actually means is: include the text of the presentation buffer
 > for the message. This is useful, because it means you can selectively
 > convert (e.g.) word attachments to text, and have them included in
 > your reply as text.

I don't deny it's useful to do stuff with the presentation; I just
think that -include-text should try harder to get all the text.  If
it's non-trivial to do that, then the MIME parser needs to be
rewritten IMO.