🚀 go-pugleaf

Kevin Rodgers <ihs_4664@yahoo.com> writes:
> Jeffrey J. Kosowsky wrote:
> 
> > OK -- this last patch solved most of my problems. But I am now
> > encountering a more subtle problem on just a few of my email
> > attachments that only affects launching programs in Windoze and not Linux.
> > Specifically, everything works fine when using oocalc/oowriter
> > etc. under Linux/Gnome to launch attached M$ documents.
> > However, when I try to read the very same email message and launch
> > the
> > same attachments under Windoze, the files are detached to my Windoze
> > temp directory but the relevant MS Office application fails to launch.
> > The problem appears to be due to characaters like "&" in the filename
> > which somehow must not get parsed properly by the windoze launcher.
> > Note I am using the following code to trigger the launch of the
> > external applications: (add-to-lists
> > 'vm-mime-external-content-types-alist
> >  (cond
> >   ((equal window-system 'x)
> >    '(("audio/x-wav" "mplayer -quiet")
> > 	 ("application/msword" "oowriter")
> > ;	 ("application/rtf" "oowriter")
> > 	 ("application/vnd.ms-powerpoint" "ooimpress")
> > 	 ("application/vnd.ms-excel" "oocalc")
> > 	 ("application/msexcel" "oocalc")
> > 	 ("application/pdf" "acroread")))
> >   ((equal window-system 'w32)
> >    '(("application" "cmd" "/C" "%f")
> > 	 ("audio" "cmd" "/c" "%f")
> > 	 ("image" "cmd" "/c" "%f")
> > 	 ("video" "cmd" "/c" "%f")))
> >   ))
> > [Note: add-to-lists is my own mapcar version of the add-to-list
> > function.]
> > Do I need to add any extra quoting somehow to make sure that the
> > filenames are passed properly?
> > [note again that the files are detached properly to the temp
> > directory, they just fail to launch the appropriate viewer
> > application]
> 
> The file name should not be quoted when it is passed directly to an
> external PROGRAM.  Since the cmd launcher is a shell, you should use the
> COMMAND-LINE syntax provided by vm-mime-external-content-types-alist to
> take advantage of the patch I posted on the 12th in this thread (which
> quotes the file name when it is passed to a shell):
> 
> ("application" "cmd /c %f")
> ("audio" "cmd /c %f")
> ("image" "cmd /c %f")
> ("video" "cmd /c %f")

Unfortunately, this does not seem to solve the problem for me. I still
get the same situation where the file is saved to the temp directory
but the application is not launched. Again, the problem is only with
files that have odd characters like '&' in them.

Note the messages buffer shows the following message:
        Launching cmd /c "c:/DOCUME~1/myname/LOCALS~1/Temp/FP&A 2004-2005
        Capabilities.ppt"... done

The problem with the '&' is confirmed because when I run the command
directly from the DOS prompt as follows:
C:> cmd /c "c:/DOCUME~1/myname/LOCALS~1/Temp/FP&A 2004-2005 Capabilities.ppt"

I get the following response:
'c:/DOCUME~1/myname/LOCALS~1/Temp/FP' is not recognized as an internal
or external command, operable program or batch file.
'A' is not recognized as an internal or external command,
operable program or batch file.

So clearly, the ampersand seems to be screwing things up.

Any suggestions?