Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: ding@gnus.org
Subject: Re: default mime for attaching files
Date: Sun, 18 Feb 2007 12:32:23 +0900	[thread overview]
Message-ID: <877iug6szc.fsf@catnip.gol.com> (raw)
In-Reply-To: <b4mmz3cqp6u.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:
> By default, Gnus uses the "inline" disposition for an attachment of
> which the MIME type is text/* except text/rtf[1].  So, the reason
> seems to be that the text/* MIME type is specified in your system
> for *.csv files.  You know how to customize it already. ;-)

Actually I've always thought that this behavior of Gnus was sort of dumb
-- I don't think it really makes sense to inline random text/ sub-types.
Glancing through the list of text/ sub-types in /etc/mime.types, most
look like the sort of thing I wouldn't want inline; in practice I also
find that I usually have to override the default (the one which annoys
most often is text/x-diff).

Instead I think Gnus should default to "attach", and have a list of
text/ sub-types which _should_ be inlined (bonus for making it a real
configurable list, not hardwired in the code...).

Thanks,

-Miles

-- 
Fast, small, soon; pick any 2.




  reply	other threads:[~2007-02-18  3:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09  0:52 Sebastian P. Luque
2007-02-09  2:00 ` Katsumi Yamaoka
2007-02-09  5:22   ` Sebastian P. Luque
2007-02-09  5:47     ` Katsumi Yamaoka
2007-02-17 23:46       ` Sebastian P. Luque
2007-02-18  0:34         ` Katsumi Yamaoka
2007-02-18  3:32           ` Miles Bader [this message]
2007-02-19 12:22             ` Katsumi Yamaoka
2007-02-19 19:49               ` Reiner Steib
2007-02-19 23:27                 ` Katsumi Yamaoka
2007-02-19 23:49                   ` Sebastian P. Luque

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=877iug6szc.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --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).