Re: Good things to put in mailcap-mime-data for NT?

Re: Good things to put in mailcap-mime-data for NT?

[Rod Whitby]

Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> Anyone that has some nice elisp/data to add to mailcap-mime-data for
> usage on WinNT? I have a .mailcap on h: but it's also ~ on our
> Solaris-system so I can't add anything Windows-specific stuff there (I
> know I can have tests in .mailcap but I want to avoid it).
> 
> As of now I can't view e.g. MS Word files without having to save them
> and then open them in Word.

What I do on XEmacs/NT to get around the whole problem of deciding
which application to launch is to get Windows to decide for me:

[This might be a useful function to add to mailcap.el ...]

(defun mailcap-mswindows-shell-execute ()
  (goto-char (point-min))
  (unwind-protect
      (let* ((dir (make-temp-name (expand-file-name "emm." mm-tmp-directory)))
	     (filename (mail-content-type-get
			(mm-handle-disposition handle) 'filename))
	     file buffer)
	;; We create a private sub-directory where we store our files.
	(make-directory dir)
	(set-file-modes dir 448)
	(if filename
	    (setq file (expand-file-name (file-name-nondirectory filename)
					 dir))
	  (setq file (make-temp-name (expand-file-name "mm." dir))))
	(message "Saving file %s ..." file)
	(let ((coding-system-for-write mm-binary-coding-system))
	  (write-region (point-min) (point-max) file nil 'nomesg))
	(message "Saving file %s ... done." file)
	(message "Loading application ...")
	(mswindows-shell-execute "open" file)    
	(message "Loading application ... done.")
	'external))
  (progn
    (ignore-errors (delete-file file))
    (ignore-errors (delete-directory
		    (file-name-directory file)))
    (ignore-errors (kill-buffer (current-buffer)))))

(mapcar
 (lambda (arg) (mailcap-add arg 'mailcap-mswindows-shell-execute))
 (list
  "application/dvi"
  "application/msword"
  "application/octet-stream"
  "application/pdf"
  "application/postscript"
  "application/ppt"
  "application/vnd.ms-excel"
  "application/vnd.ms-powerpoint"
  "application/x-mspowerpoint"
  "application/x-msword"
  "application/x-powerpoint"
  "application/x-zip-compressed"
  "application/zip"
  ))


-- 
-- Rod Whitby, Snr Staff Engr, Electronic Design Automation --
-- Motorola Australia Software Centre - Adelaide, Australia --
-- Phone: +61 8 8168 3526, Fax: +61 8 8168 3501, <GMT+9:30> --

Re: Good things to put in mailcap-mime-data for NT?

[Rod Whitby]

Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> Rod Whitby <list.ding@rwhitby.net> writes:
> > Jonas Steverud <d4jonas@dtek.chalmers.se> writes:
> > > Anyone that has some nice elisp/data to add to mailcap-mime-data for
> > > usage on WinNT?
> 
> [...]
> > What I do on XEmacs/NT to get around the whole problem of deciding
> > which application to launch is to get Windows to decide for me:
> [...]
> > (defun mailcap-mswindows-shell-execute ()
> [...]
> > 	(mswindows-shell-execute "open" file)    
> 
> Is that a function that comes with XEmacs? I couldn't find it in
> NTEmacs/Gnus (I can't say wich version I use since I'm not at my
> office on a sunday evening...). Otherwise ot looks good code.

Yes, that's an XEmacs function.  But it should be available on all NT
Emacsen (or should be easy for someone to add if it's not).  I believe
it pretty much maps straight to a single Windows call.

-- 
-- Rod Whitby, Snr Staff Engr, Electronic Design Automation --
-- Motorola Australia Software Centre - Adelaide, Australia --
-- Phone: +61 8 8168 3526, Fax: +61 8 8168 3501, <GMT+9:30> --

Re: Good things to put in mailcap-mime-data for NT?

[Kai Großjohann]

On 06 Aug 2000, Jonas Steverud wrote:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>> application/msword; start %s
> 
> Since I rarely need to use .mailcap on Solaris I currently use this
> scheme but I have problems with files that contains a space.

Well, maybe this one does the trick.  But I don't use Windows.

application/msword; start "%s"

Maybe Gnus should run shell-quote-argument on the filename before
passing it to the command.

kai
-- 
I like BOTH kinds of music.

Re: Good things to put in mailcap-mime-data for NT?

[Kai Großjohann]

On 11 Aug 2000, Jonas Steverud wrote:

> Didn't work:
> 
> Displaying start "c:/TEMP/emm.228xNB/127 02-.doc"...

And is `127 02-.doc' the right file name?  The trailing dash looks
suspicious.

Does it work to save the `127 02-.doc' file somewhere manually, then
open a DOS box and type `start "c:/path/to/dir/127 02-.doc"'?  If this
doesn't work, what command line do you need to have Word open the
file? 

A workaround might be to edit the message and to change the file name,
before invoking Word on it.

kai
-- 
I like BOTH kinds of music.

Re: Good things to put in mailcap-mime-data for NT?

[Kai Großjohann]

On 14 Aug 2000, Jonas Steverud wrote:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>> On 11 Aug 2000, Jonas Steverud wrote:
>> 
>> > Didn't work:
>> > 
>> > Displaying start "c:/TEMP/emm.228xNB/127 02-.doc"...
>> 
>> And is `127 02-.doc' the right file name?
> 
> It is.
> 
>> Does it work to save the `127 02-.doc' file somewhere manually,
>> then open a DOS box and type `start "c:/path/to/dir/127 02-.doc"'?
> 
> Nope.
> 
> It worked if I saved it to 12702-.doc and then did:
> 
> prompt> start 12702-.doc

Well.  Hm.  Does this work, too?

prompt> start "12702-.doc"

If this fails, then the quotes are a problem.  Hm.  I thought DOS
would accept quotes like this, but I know really nothing about DOS.

kai
-- 
I like BOTH kinds of music.

Re: Good things to put in mailcap-mime-data for NT?

[Kai Großjohann]

On 15 Aug 2000, Jonas Steverud wrote:

> I think we both are thinking in *nix-terms. Dos does *nothing* with
> the command line before passing it to the program.

I thought that COMMAND.COM did _almost_ nothing, the single exception
being double quote processing, which is needed for file names
containing spaces.

But then, I haven't seen DOS in a long while now, not even from afar.

kai
-- 
I like BOTH kinds of music.

Re: Good things to put in mailcap-mime-data for NT?

[Florian Weimer]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> > I think we both are thinking in *nix-terms. Dos does *nothing* with
> > the command line before passing it to the program.
> 
> I thought that COMMAND.COM did _almost_ nothing, the single exception
> being double quote processing, which is needed for file names
> containing spaces.

COMMAND.COM does nothing.  The DOS (and Windows) command line
consists of exactly one argument (at least the last time I looked,
approximately five years ago :-/).  Parsing is done entirely by the
application, and wildcard processing as well.