Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Cc: ding@gnus.org
Subject: Re: p0.88 misparses 2nd-level message forwarding
Date: 22 Jun 1999 21:10:10 -0400	[thread overview]
Message-ID: <2naetrafil.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <vxk674gj5tz.fsf@beaver.jprc.com>

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

>>>>> "KK" == Karl Kleinpaste <karl@justresearch.com> writes:

KK> 1. Send yourself a test message -- normal message, text/plain.
KK> 2. Forward that message to yourself -- an inline message/rfc822.
KK> 3. Forward *that* message to yourself.
KK> You now have an inline message/rfc822 containing another inline
KK> message/rfc822.

KK> p0.88's display of this will be...confused.

KK> Assuming that you prefix each forwarding with a bit of text/plain as
KK> well, you will see:

KK>         [1. text/plain]
KK>         containing the "outermost" (3rd level) new text.

KK>         [2. message/rfc822]
KK>         containing nothing but (in my case) an X-Sent: header (which BTW
KK>         erroneously duplicates the topmost X-Sent; I sent a bug report
KK>         about this last week).

KK>         [3. text/plain]
KK>         containing the 2nd level text which prefaced the original message
KK>         on 1st forwarding...  *followed by* the entire remaining message
KK>         displayed as text/plain, including both the 2nd level and 1st
KK>         level messages...  all as part of a single "3." section.

KK>         [4. message/rfc822]
KK>         containing the original, 1st level forwarded message.

KK> Note that the innermost, original text is duplicated in both the
KK> 3. and 4. sections.

Try this patch.

1999-06-22  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* mm-view.el (mm-inline-message): Fix message view bug.
	* gnus-art.el (gnus-article-prepare): Ditto.


[-- Attachment #2: 88-zsh8.diff --]
[-- Type: application/x-patch, Size: 1379 bytes --]

[-- Attachment #3: Type: text/plain, Size: 483 bytes --]


KK> Perhaps significantly, the buttonized (`K b') display of these
KK> sections will show the button areas as
KK>         [1. text/plain] in *bold*
KK>         [2. message/rfc822] in *bold*
KK>         [3. text/plain] in /italic/
KK>         [4. message/rfc822] in *bold*
KK> Shouldn't these be labelled something hierarchical anyway, such as 1., 
KK> 2., 2.1, 2.2, 2.2.1?

It is difficult. The label is used as the argument of
gnus-article-view-part (press 'b').

-- 
Shenghuo ZHU

  reply	other threads:[~1999-06-23  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-22 21:14 Karl Kleinpaste
1999-06-23  1:10 ` Shenghuo ZHU [this message]
1999-06-23  1:28   ` Karl Kleinpaste
1999-06-28 17:32     ` 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=2naetrafil.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    --cc=ding@gnus.org \
    /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).