Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@danann.net>
Subject: Re: Showing image attachments inline, but buttonized
Date: 23 Apr 2000 12:51:10 +1000	[thread overview]
Message-ID: <878zy5wmw1.fsf@inanna.pangaean.net> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 22 Apr 2000 20:28:59 +0200"

On Sat, 22 Apr 2000, Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
wrote:

[...]

> Hi there, could we do some brainstorming on when to add dividing
> lines?
> 
>   - Add them before and after a message/* part.
>   - Don't add them before a part that's on the same line.
>   - Add them between a text/foo and a text/bar part where foo not
>     equal bar.

FWIW, I only feel a great need to have dividing lines around message/*
parts - the rest of them can flow seamlessly as far as I am concerned.

Why? Because message/* parts are complex entities, while the others are
parts of a complex entity. I have not yet seen any other type where I
really got into trouble understanding the structure of it, except for
embedded message/* parts.[1]

        Daniel


Footnotes: 
[1]  Not even them these days, because I push my own dividing lines in. :)

-- 
The desire to belong is partly the desire to lose oneself.
        -- Eric Hoffer



      reply	other threads:[~2000-04-23  2:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-24 11:52 Hrvoje Niksic
1999-12-01 20:41 ` Lars Magne Ingebrigtsen
1999-12-02  8:24   ` Hrvoje Niksic
1999-12-02 23:12     ` Lars Magne Ingebrigtsen
1999-12-03  8:03       ` Hrvoje Niksic
2000-04-21 23:34         ` Lars Magne Ingebrigtsen
1999-12-02 12:10   ` Toby Speight
1999-12-02 23:12     ` Lars Magne Ingebrigtsen
1999-12-05 21:48   ` Kai Großjohann
2000-04-21 23:34     ` Lars Magne Ingebrigtsen
2000-04-22 15:53       ` Kai Großjohann
2000-04-22 18:27         ` Lars Magne Ingebrigtsen
2000-04-22 18:28           ` Kai Großjohann
2000-04-23  2:51             ` Daniel Pittman [this message]

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=878zy5wmw1.fsf@inanna.pangaean.net \
    --to=daniel@danann.net \
    /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).