From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: MIME handling for common MS Windows attachments?
Date: 13 Jan 1999 13:16:38 -0500 [thread overview]
Message-ID: <86iuebox6h.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Matt Armstrong's message of "13 Jan 1999 09:12:35 -0800"
Matt Armstrong <mattdav+matt@best.com> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> > Hrvoje Niksic <hniksic@srce.hr> writes:
> >
> > > I still think relieving users by defaulting ms-word to MS Word
> > > viewers, etc., might be useful, even if strictly against FSF's
> > > philosophy.
> >
> > I think so, to. Defaulting *.doc to ms-word is bad, but I see no harm
> > in defaulting application/ms-word to MS Word (or something else that
> > can understand these files).
>
> I think defaulting .doc to ms-word is good when running under Win32.
>
> Anyway, Debian Linux has an /etc/mime.types file that does what
> mailcap.el's mailcap-mime-extensions does. I'm not sure how Debian
> specific it is, but are people open to having Gnus look for it (or
> maybe a ~/.mime.types file)?
The old 'mm.el' stuff that lars based his mime decoding stuff on
supported this. This is a very standard file, dating back to the dark
ages. :)
> > A more sticky issue is whether to default image/* to the un-free,
> > but commonly installed xv, or to some free image viewing program.
> >
> > What image viewing programs exist out there?
> >
> > (Well, it isn't really a sticky issue, because we could default to
> > free programs, and then use non-free programs as the backup default
> > values if the free programs don't exist on the system.)
>
> I assume that files like /etc/mailcap override Gnus' defaults?
It should, and ~/.mailcap overrides it.
-bp
next prev parent reply other threads:[~1999-01-13 18:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 14:46 John Cooper
[not found] ` <m37lusset2.fsf@peorth.gweep.net>
1999-01-12 16:28 ` Hrvoje Niksic
1999-01-12 17:25 ` Lars Magne Ingebrigtsen
1999-01-12 19:07 ` Karl Eichwalder
1999-01-12 19:37 ` Hrvoje Niksic
1999-01-15 17:56 ` Karl Eichwalder
1999-01-12 19:13 ` Hrvoje Niksic
1999-01-13 7:51 ` Steinar Bang
1999-01-13 9:38 ` Russ Allbery
1999-01-13 14:13 ` Karl Kleinpaste
1999-01-13 15:50 ` Alan Shutko
1999-01-13 18:43 ` Lars Magne Ingebrigtsen
1999-01-14 0:58 ` Russ Allbery
1999-01-14 16:14 ` Hrvoje Niksic
1999-01-13 17:12 ` Matt Armstrong
1999-01-13 18:16 ` William M. Perry [this message]
1999-01-13 15:54 ` Robert Pluim
1999-01-13 16:27 ` William M. Perry
1999-01-13 22:35 ` Kai.Grossjohann
1999-01-14 11:53 ` John Cooper
1999-01-14 12:51 ` John Cooper
1999-01-14 15:14 ` Robert Bihlmeyer
1999-01-14 15:25 ` Robert Pluim
1999-01-14 19:20 ` Lars Magne Ingebrigtsen
1999-01-14 20:10 ` William M. Perry
1999-01-14 21:12 ` 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=86iuebox6h.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.com \
--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).