Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Bihlmeyer <e9426626@stud4.tuwien.ac.at>
Subject: Re: Display of inline messag/rfc822 (aka MIME forwards)
Date: 08 Oct 1999 18:25:31 +0200	[thread overview]
Message-ID: <lfn1ttddl0.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: François Pinard's message of "04 Oct 1999 20:20:36 -0400"

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]

Hi,

>>>>> On 04 Oct 1999 20:20:36 -0400
>>>>> François Pinard <pinard@iro.umontreal.ca> said:

 FP> These principles are fruitful for cases like in-lined
 FP> message/rfc822. I'm including a picture of your demonstration,
 FP> below. For me, it is absolutely clear that I'm looking at a
 FP> quoted message.

for me, it's not. It could be a colored message body (text/enriched,
text/html). Furthermore, my headers are not colored in all
configurations (think: vt220), so in this cases the message/message
boundary is even more elusive.

 FP> When the message has signature, which is the usual case, such
 FP> problems do not exist, as Gnus uses a pretty characteristic
 FP> rendering for signatures.

Again, not in all configurations. Also, denying the problem for "the
usual case", which is not so usual in my opinion (broken mailers
abound), will not make it go away.

 FP> Maybe that Gnus could invent a mere `-- ' (rendered as a
 FP> signature) when rendering a message/rfc822 in a MIME part, which
 FP> has no recognised signature?

That could be a solution. But is it workable in most configurations?

 FP> Here is the promised picture:

FWIW, I don't consider sending messages > 500 lines without asking
first good etiquette.

	Robbe

-- 
Robert Bihlmeyer	reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at>	<http://stud2.tuwien.ac.at/~e9426626/sig.html>


  reply	other threads:[~1999-10-08 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-20 10:34 Robert Bihlmeyer
1999-09-22 22:01 ` Jack Vinson
1999-09-22 22:18   ` Simon Josefsson
1999-10-04 12:41   ` Robert Bihlmeyer
1999-11-06  2:53     ` Lars Magne Ingebrigtsen
1999-10-05  0:20 ` François Pinard
1999-10-08 16:25   ` Robert Bihlmeyer [this message]
1999-10-11 22:29     ` François Pinard
1999-11-06  3:00       ` 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=lfn1ttddl0.fsf@mars.zserv.tuwien.ac.at \
    --to=e9426626@stud4.tuwien.ac.at \
    /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).