Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: ding@gnus.org
Subject: Re: Display of inline messag/rfc822 (aka MIME forwards)
Date: 04 Oct 1999 20:20:36 -0400	[thread overview]
Message-ID: <oq1zbapsiz.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Robert Bihlmeyer's message of "20 Sep 1999 12:34:36 +0200"

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

Robert Bihlmeyer <e9426626@stud4.tuwien.ac.at> writes:

> per default, inline parts have no visual separation from other inline
> parts.  This is arguably correct for normal parts, but very wrong for
> message/rfc822, at least.

> The only indication that an inlined (forwarded) message/rfc822 starts
> is the sudden appearance of mail headers.

I'm all for the principle than underline should mean clickable, more or less.
I render _underline_ with a yellow background ("seashell1", to be precise),
to simulate what we call a `crayon à souligner' in French (I think English
people say "underlining pen" or "highlighting pen").  Plain bold should not
be abused when avoidable, and I prefer to use background colouring instead.

> this is a demonstration.

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

> There is no indication of the message's end, whatsoever.

Here, you have a point.  I do see a plain:

   (this is the last line of the inner message)
   (we're in the outer message, again)

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

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

Here is the promised picture:


[-- Attachment #2: demo.png --]
[-- Type: image/png, Size: 66912 bytes --]

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


-- 
François Pinard   http://www.iro.umontreal.ca/~pinard

  parent reply	other threads:[~1999-10-05  0:20 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 [this message]
1999-10-08 16:25   ` Robert Bihlmeyer
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=oq1zbapsiz.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --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).