help-emacs-windows
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jeff Rancier
Subject: RE: [h-e-w] shell-command
Date: Thu, 18 Oct 2001 08:59:01 -0400

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?
Jeff

-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of Matt McClure
Sent: Wednesday, October 17, 2001 5:18 PM
To: address@hidden
Subject: Re: [h-e-w] shell-command


On Wed Oct 17 2001, 16:51, Wojciech Komornicki <address@hidden>
wrote:

> The syntax for the shell-command function is
>       shell-command is an interactive compiled Lisp function in `simple'.
>       (shell-command COMMAND &optional OUTPUT-BUFFER ERROR-BUFFER)
> To not have an output buffer, set the last two arguments to nil,
> i.e. call your function as
>      (shell-command
>         (concat "start "
>
"file:///H:/usr/pkg/jakarta-ant-1.4.1/docs/manual/index.html/")
>         nil nil)

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?

--
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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]