Re: [h-e-w] shell-command

[Matt McClure]

On Thu Oct 18 2001, 08:59, "Jeff Rancier" <address@hidden>
wrote:

> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden Behalf Of Matt McClure
> > Sent: Wednesday, October 17, 2001 5:18 PM
> > To: address@hidden
> > 
> > Calling shell-command with the OUTPUT-BUFFER argument equal to nil makes
> > the output go to *Shell Command Output*.  Does
> > 
> > (start-process "" nil "start"
> >     "file:///H:/usr/pkg/jakarta-ant-1.4.1/docs/manual/index.html/")
> > 
> > work instead?
>
> That's better, except I need to define an explicit path for *start*.
> I can't seem to find it, I guess it's path of the command processor?

It seems I don't have a start.exe either (Windows 2000).  From the looks
of what you were trying to do, I'm guessing it's supposed to open the
specified file with the application associated with that file type.
Does "cmd /c" work for you?

-- 
Matt
http://www.faradic.net/~mmcclure/

    "I don't believe in rivalries.  I don't believe in curses.  Wake
     up the damn Bambino, maybe I'll drill him in the (behind)."
        -Pedro Martinez