🚀 go-pugleaf

Jeffrey J. Kosowsky wrote:
 > Kevin Rodgers <ihs_4664@yahoo.com> writes:
 >>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?

It might be that VM is using the file name that was cached in the MIME
layout, instead of the quoted file name.  What does this return on your
platform:

	(shell-quote-argument
	 "c:/DOCUME~1/myname/LOCALS~1/Temp/FP&A 2004-2005 Capabilities.ppt")

Also, what happens if you leave off the %f spec so that
vm-mime-display-external-generic adds the quoted name itself:

	("application" "cmd /c")
	("audio" "cmd /c")
	("image" "cmd /c")
	("video" "cmd /c")

-- 
Kevin Rodgers