[mew-int 00525] mew-summary-pipe-message and mew-summary-display-asis

[sen_ml at example.com]

From: Kazu Yamamoto (山本和彦) <kazu at example.com>
Subject: Re: mew-summary-pipe-message, Mew 2.1rc2, and Emacs 21.1
Date: Mon, 29 Oct 2001 16:00:55 +0900 (JST)

> From: sen_ml at example.com
> Subject: [mew-int 00520] Re: mew-summary-pipe-message, Mew 2.1rc2, and Emacs 21.1
> 
> >   When using "cat" with mew-summary-pipe-message, I expect to see the
> >   content of the message in text form (no mark-up), in other words how
> >   the file would appear when viewing it using "less".
> 
> Sorry, I don't understand.

Hmmm, I wonder how I can explain better.

Ok, I believe your statement about what I sent not being rich text
format.  The file was the result of saving a document in Abiword 0.9.0
as "Rich Text Format .rtf" -- FWIW, similarly created files were
readable using M$ Word.

So, given what you have said about rich text format, here are revised
instructions:

1) Using Abiword 0.9.0, create a non-empty document and save it as
   "Rich Text Format .rtf".  Alternatively, save the attachment
   I sent earlier -- perhaps naming it something like "test.rtf" --
   as it is the result of the same set of operations (i.e. using
   Abiword).

2) Send yourself a message containing the file created in step
   1) as an attachment.

3) Retrieve the message with the attachment.

4) View the message using ",".

5) Now run mew-summary-pipe-message and choose "cat" as the command to
   execute.  N.B. It appears that viewing other messages between this
   step and the previous step affect the results in some cases.

I had a fellow Mew user test using Mew 2.0.53 and Emacs 20.7 with an
appropriate message which I sent him, and he was also able to
experience part of the problem, except that in his case, some of the
mark-up did not appear -- however, he also had:

Content-Type: text/enriched
Text-Width: 70

at the beginning of his shell output for cat.

I hope the problem is now reproducable on your end.