Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: Re: Un-MIMEified MIME message
Date: 04 Mar 1999 11:30:37 -0600	[thread overview]
Message-ID: <wkww0xjh6q.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Tue, 02 Mar 1999 19:00:32 +0100"

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:
>> When I got to the text/html part, the ellipses appeared after the button,
>> but the text did not hide.  When I clicked the button again, new text
>> appeared and the old text remained.  Repeating this cycle caused multiple
>> entries of the same text, over and over. 

LMI> Hm.  I did get some rather weird results when doing this, but not
LMI> exactly what you describe.  But this may be fixed in 0.80.

This has not been corrected in 0.80.  I notice it (the problem) even before
I buttonize my buffer.  With the inlined parts, the words "*second*" and
"third" appear on the same line with a bold "*second*", followed by regular
font "third." 

Again, when I repeatedly whack the third button (text/html) it does not get
displayed correctly.

Here is another interesting feature.  If I C-d the article, the new summary
looks like this:
E  [  40: *Lars Magne Ingebrig] <* mixed> Re: Un-MIMEified MIME message
E      [   7: *Lars Magne Ingebrig] <1 text>
E      [  23: *Lars Magne Ingebrig] <2.* mixed>
E          [   0: *Lars Magne Ingebrig] <2.1 text>
E          [   2: *Lars Magne Ingebrig] <2.2 html>
E          [   0: *Lars Magne Ingebrig] <2.3 text>
E          [   4: *Lars Magne Ingebrig] <2.4 text>

Note that parts 1 and 3 have a Zero line count.  

And when I look at the raw article, the text/plain parts have no
Content-Type header.  I take it the default is text/plain when nothing is
specified?


-- 
Jack Vinson <jvinson@chevax.ecs.umass.edu>    http://www.cis.upenn.edu/~vinson/
Zippy: It was a JOKE!!  Get it??  I was receiving messages
 from DAVID LETTERMAN!!  YOW!!



  reply	other threads:[~1999-03-04 17:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-25 16:16 Shane Holder
1999-02-25 17:53 ` Kai.Grossjohann
1999-02-25 19:23   ` Shane Holder
1999-02-26 15:50     ` Kai.Grossjohann
1999-02-26 16:41       ` Lars Magne Ingebrigtsen
1999-02-26 17:20         ` Shane Holder
1999-02-26 17:29           ` Lars Magne Ingebrigtsen
1999-03-01 19:24             ` Jack Vinson
1999-03-02 18:00               ` Lars Magne Ingebrigtsen
1999-03-04 17:30                 ` Jack Vinson [this message]
1999-03-04 21:02                   ` James H. Cloos Jr.
1999-03-05 20:11                   ` Lars Magne Ingebrigtsen
1999-03-22 21:47             ` Jack Vinson
1999-03-23 17:28               ` Kai.Grossjohann
1999-03-28 17:14               ` Lars Magne Ingebrigtsen
1999-02-27  9:50           ` Hans de Graaff
1999-02-26 17:23         ` Kai.Grossjohann
1999-02-26 17:53           ` Lars Magne Ingebrigtsen
1999-02-26 18:13             ` Kai.Grossjohann
1999-02-26 18:26               ` Lars Magne Ingebrigtsen
1999-02-26 18:31               ` Lars Magne Ingebrigtsen
1999-02-26 15:51     ` Kai.Grossjohann
     [not found]       ` <uyall5c3h.fsf@rsn.hp.com>
1999-02-26 17:19         ` Kai.Grossjohann
1999-02-26 14:38 ` Lars Magne Ingebrigtsen

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=wkww0xjh6q.fsf@chevax.ecs.umass.edu \
    --to=jvinson@chevax.ecs.umass.edu \
    /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).