Hi.

arpep...@uwaterloo.ca wrote in
<20200617204855.44a584162...@ubuntu1804-102.cs.uwaterloo.ca>:
 |Well, I received this from the list, and I could view the
 |cartoon.jpg in the 1990's mail reader of which I spoke.

Yes, that was possible. ;)

 |I was also able to view the attachment by saving the text
 |to a file and using "base64 -d" etc.
 |
 |Here is a session trying to use s-nail (s-nail v14.9.6)  however...

But please, i have said that the bug you encounter had been fixed
in v14.9.9 as of March 2018!

 |(inline text inclusion by indenting three spaces...)

Nice :)

 |   & set pipe-image/jpeg=' display -font fixed '
 |   & mimeview
 |   [-- Message 301 -- 4237 lines, 322396 bytes --]:
 |   From s-mailx-boun...@sdaoden.eu Wed Jun 17 16:22:59 2020
 |   X-Spam-Status: No, score=-5.2 required=4.0
 |   tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE
 |   autolearn=ham autolearn_force=no version=3.4.2
 |   Delivered-To: s-mailx@lists.sdaoden.eu
 |   From: arpep...@uwaterloo.ca
 |   To: s-ma...@sdaoden.eu
 |   Date: Wed, 17 Jun 2020 15:20:46 -0400 (EDT)
 |   Subject: [S-mailx] Can you view the attachment to this message?
 |   X-Virus-Status: Clean
 |
 |
 |   [-- No MIME handler installed, or not applicable --]
 |
 |

Yeah it looks terrible.  That is the recursive parser we use,
recursive parsers are no good.  At least not if used like here.
(The shell maybe needs to parse $( .. ) construct recursive, but
these are mail messages, sigh.)
In v15 this will be much better.  At least optically.

 |   [-- #1.2 4130/317709 image/jpeg, base64, us-ascii --]
 |   [-- cartoon.jpg --]
 |   Run MIME handler for this part? [no]/yes? yes  
 |   display-im6.q16: Corrupt JPEG data: 1185 extraneous bytes before marker
 |   0x03 `/tmp/magick-7219o0A-RaVoYzMa' @
 |   warning/jpeg.c/JPEGWarningHandler/352.
 |   display-im6.q16: Unsupported marker type 0x03
 |   `/tmp/magick-7219o0A-RaVoYzMa' @ error/jpeg.c/JPEGErrorHandler/322.
 |   &
 |
 |The mention of "0x03" is consistent with other errors I saw
 |while experimenting.  With the real problem probably being
 |some missing "015" characters being (not) sent to the 
 |"display" program.

Yes.  Unfortunately small and rapidly moving projects become
penalized in those long term stability things.  In those over two
years in between v14.9.9 and v14.9.19 hundreds and more bugs have
been fixed, but they will not upgrade it.  You had to backport all
bug fixes, and that is sometimes even impossible, but anyway, i do
not have ressources for such an effort.  Sorry.

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

Reply via email to