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: 11 Oct 1999 18:29:43 -0400	[thread overview]
Message-ID: <oqyad95y5k.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: Robert Bihlmeyer's message of "08 Oct 1999 18:25:31 +0200"

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

> >>>>> 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).

Tss, tss...  You might not be playing honest, here.  For that matter,
whatever aspect you decide as being clear enough, one could generate some
enriched text that would look exactly like it.  It is extremely unlikely,
besides someone making practical jokes, that I would receive a message
that would just happen to look like a quoted message, in the picture you saw.

> 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.

Quite agreed.  This is why Gnus is so tunable and adaptable.  Gnus should
model its usual behaviour after the most usual cases (yet within reason,
of course).  Tuning and customisation exist for the less usual cases.

>  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?

Yes, in my feelings, but this proves nothing. :-) If it sounds reasonable
to most people, and to Lars as well, maybe he will adopt it?

>  FP> Here is the promised picture:

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

The ding list is for discussing about news and messages, by people
interested in such matters, participating in a development effort.
Asking permission before sending a message, given the time a poll would
take, and the discussions around it, would easily generate more volume
than the message itself, not to say how inefficient and counter-productive
the whole thing would be.  I do not feel I exaggerated in that situation,
at least in the context of the ding list.  I had something to show you,
and I merely used the methods Gnus gives me to do so, and the message
was aimed to people using similar tools.  My impression is that it is OK.
And a few Kbs are not inordinate.  We are far from speaking Megs, here :-).

Of course, I could establish an Internet connection, move files around onto
some FTP site, etc., but that's a lot of burden for a straight and simple
thing.  I would rather abstain than to go through that hassle.  In any case,
if there is a consensus I did wrong, just tell me, and I'll adjust.

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



  reply	other threads:[~1999-10-11 22:29 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
1999-10-11 22:29     ` François Pinard [this message]
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=oqyad95y5k.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).