From: Steinar Bang <sb@metis.no>
Subject: Re: No more buttons by default?
Date: 20 Nov 1998 14:15:23 +0100 [thread overview]
Message-ID: <whsofe4iac.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Hrvoje Niksic's message of "20 Nov 1998 11:25:48 +0100"
>>>>> Hrvoje Niksic <hniksic@srce.hr>:
> All this is bad news. I don't really buy into this equivalence of
> MIME and HTML that you people so like to stress. MIME simply
> provides a clean way of merging all these formats and a clean way of
> specifying how you want them shown; it is by no means the equivalent
> of a markup language. Saying "MIME is like HTML" is IMO missing the
> point of MIME.
I'm not sure what to think. I think the proponents of MIME/HTML
equivalence are correct in that this is closer to the original MIME
idea.
But I worry that this behaviour will make us incompatible with other
MUAs that don't use the content-disposition header to tell us whether
this is an inline mime type or an attachment.
I think MIME-as markup may be workable, or maybe even the best
behaviour if we have
Content-Disposition: inline
in the message parts.
But I think Gnus should default to attachment behaviour, in the
absense of content-disposition headers, because that's probably closer
to what the composing MUA expects.
IMHO, of course!
- Steinar
next prev parent reply other threads:[~1998-11-20 13:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-15 1:01 Pterodactyl Gnus v0.46 is released Lars Magne Ingebrigtsen
1998-11-15 21:49 ` Graham Murray
1998-11-16 8:18 ` Graham Murray
1998-11-17 23:38 ` Lars Magne Ingebrigtsen
1998-11-18 3:17 ` Alexandre Oliva
1998-11-18 6:36 ` Lars Magne Ingebrigtsen
1998-11-18 6:53 ` Alexandre Oliva
1998-11-18 7:27 ` Lars Magne Ingebrigtsen
1998-11-18 7:36 ` Alexandre Oliva
1998-11-18 8:12 ` Lars Magne Ingebrigtsen
1998-11-18 8:22 ` Kai.Grossjohann
1998-11-18 8:42 ` Lars Magne Ingebrigtsen
1998-11-18 21:57 ` François Pinard
1998-11-19 5:57 ` Lars Magne Ingebrigtsen
1998-11-19 11:31 ` Hrvoje Niksic
1998-11-19 11:46 ` Lee Willis
1998-11-19 11:50 ` Hrvoje Niksic
1998-11-20 1:51 ` Lars Magne Ingebrigtsen
1998-11-19 16:23 ` François Pinard
1998-11-19 21:01 ` Edward J. Sabol
1998-11-19 22:29 ` François Pinard
1998-11-20 1:57 ` Lars Magne Ingebrigtsen
1998-11-20 10:25 ` No more buttons by default? Hrvoje Niksic
1998-11-20 13:15 ` Steinar Bang [this message]
1998-11-20 15:37 ` Lars Magne Ingebrigtsen
1998-11-20 17:30 ` Karl Kleinpaste
1998-11-20 17:45 ` Steinar Bang
1998-11-20 17:48 ` Steinar Bang
1998-11-21 4:29 ` Lars Magne Ingebrigtsen
1998-11-21 8:12 ` Dale Hagglund
1998-11-21 8:49 ` Lars Magne Ingebrigtsen
1998-11-21 9:19 ` Dale Hagglund
1998-11-21 18:14 ` Matt Armstrong
1998-11-20 15:13 ` François Pinard
1998-11-22 12:06 ` Hrvoje Niksic
1998-11-24 9:29 ` Lars Magne Ingebrigtsen
1998-11-20 15:28 ` Lars Magne Ingebrigtsen
1998-11-20 17:56 ` Raja R Harinath
1998-11-20 18:07 ` Kai.Grossjohann
1998-11-21 4:31 ` Lars Magne Ingebrigtsen
1998-11-20 12:19 ` Pterodactyl Gnus v0.46 is released Kai.Grossjohann
1998-11-20 12:35 ` Kai.Grossjohann
1998-11-20 15:26 ` François Pinard
1998-11-20 12:12 ` Kai.Grossjohann
1998-11-20 15:17 ` François Pinard
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=whsofe4iac.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).