Gnus development mailing list
 help / color / mirror / Atom feed
From: "John Cooper" <John.Cooper@citrix.com>
Cc: ding@gnus.org
Subject: Re: MIME handling for common MS Windows attachments?
Date: 14 Jan 1999 11:53:21 +0000	[thread overview]
Message-ID: <uvhiacbpq.fsf@TENDLE.citrix.com> (raw)
In-Reply-To: Robert Pluim's message of "Wed, 13 Jan 1999 16:54:10 +0100 (CET)"

Robert Pluim <rpluim@nortelnetworks.com> writes:

 > >>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:
 > 
 >     Hrvoje> Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
 >     >> "JC" == John Cooper <John.Cooper@citrix.com> writes:
 >     >>
 >     JC> By default pGnus doesn't seem to offer to attempt external
 >     JC> display of common Microsoft attachments, e.g., MS Word (MIME
 >     JC> type application/msword), excel, powerpoint, etc.
 >     >>
 >     >> That would more or less be because that is the way RMS wants it
 >     >> to be.  Supporting non-free software out of the box goes
 >     >> against the philosophy of the FSF.
 > 
 >     Hrvoje> I still think relieving users by defaulting ms-word to MS
 >     Hrvoje> Word viewers, etc., might be useful, even if strictly
 >     Hrvoje> against FSF's philosophy.
 > 
 > How about defaulting to running "start" on Mickeysoft platforms, which will
 > generally Do The Right Thing, and will allow users to change things
 > without having to mess with mailcap files ? (but have mailcap be
 > preferred, obviously).

I'm currently able to send application/msword attachments to Word; however, I
also get a lot of Word attachments from Outlook users with a MIME type
application/octet-stream, which I now manually save to disk and then invoke
`cmd /c start' on them from a zsh shell window.

How easy would it be to add a new "MIME part" menu option "Save and start...",
which calls "start" (or "cmd /c start") on the saved file?  This would make
launching attachments in NT Emacs much more convenient.

    --- John



  parent reply	other threads:[~1999-01-14 11:53 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
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 [this message]
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=uvhiacbpq.fsf@TENDLE.citrix.com \
    --to=john.cooper@citrix.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).