From: Peter Davis <pd@world.std.com>
Subject: Re: A bunch of MIME question: Some MIME parts not button-ized!
Date: Thu, 06 Feb 2003 17:16:26 -0500 [thread overview]
Message-ID: <n0l912dh.fsf@bitstream.com> (raw)
In-Reply-To: <84y94t6stq.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Peter Davis <pd@world.std.com> writes:
>
>> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>>
>>> Peter Davis <pd@world.std.com> writes:
>>>
>>>> I received a message this morning that was sent from Microsoft
>>>> "Lookout". The message had alternative text/plain and text/html
>>>> parts, and also contained two image/jpeg attachments. However, Gnus
>>>> gave me *no* indication that the JPEG attachments were even there.
>>>> There were no buttons in the *Article* buffer to indicate their
>>>> presence. My only hints were that the line count of the file was up
>>>> above 6000 for what seemed to be a very short message, and that it
>>>> took a long time to display.
>>>
>>> Gnus shows "(42 parts)" in the mode line of the article buffer for a
>>> message with many parts.
>>
>> Didn't see that. There weren't *that* many parts.
>
> Well, it shows "(2 parts)" for a message with few parts :-)
Aha! I was looking at the bottom mode line (under the BBDB buffer),
but this was on the mode line under the *Article* buffer. Thanks.
>
>>> You can use C-d on it to debug the MIME structure.
>>
>> What function is this supposed to invoke? On my system, C-d runs
>> gnus-summary-enter-digest-group.
>
> That's right. Same here. Have you tried it on a MIME message? I
> think it's way cool.
Way cool is right! Here's what I found:
.+[6321: Some Person ] 06-Feb <* related> RE: The subject of this
.+ [ 188: Some Person ] 06-Feb <1.* alternative>
.+ [ 50: Some Person ] 06-Feb <1.1 text>
.+ [ 125: Some Person ] 06-Feb <1.2 html>
.+ [3090: Some Person ] 06-Feb <2 jpeg> "image001.jpg"
.+ [3023: Some Person ] 06-Feb <3 jpeg> "image002.jpg"
It appears the images were *not* part of a multipart/related, so I
don't know if there's any way to have gotten W3 to display them.
>>> You can use K b to see buttons, and then switch from text/plain to
>>> text/html. I'm not sure if it works, but I think that rendering
>>> text/html with W3 means you get to see the images, too. (I'm
>>> guessing that the text/html alternative was a multipart/related which
>>> contained three subparts for the text and the two images.)
>>
>> I'll try this. In this case, I didn't see any buttons for the HTML
>> alternative or for the attached JPEG files. I'll try 'K b' next
>> time. In the past, W3 has seemed very slow to me, though perhaps this
>> is from trying to fetch things I'd rather not have fetched anyway.
>> (There's a way to disable remote fetches, isn't there?)
>
> I guess that W3 renders slowly. I've replaced it with emacs-w3m.
> Maybe I should go back to W3 someday to see what has happened with it.
And I'll have to try w3m again. I never managed to get it working.
Thanks!
-pd
--
--------
Peter Davis
Funny stuff at http://www.pfdstudio.com
The artwork formerly shown as prints
List of resources for children's writers and illustrators at:
http://www.pfdstudio.com/cwrl.html
parent reply other threads:[~2003-02-06 22:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <84y94t6stq.fsf@lucy.is.informatik.uni-duisburg.de>]
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=n0l912dh.fsf@bitstream.com \
--to=pd@world.std.com \
/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).