Nick Fortune <[EMAIL PROTECTED]> writes:
> On Tue, Jun 07, 2005 at 10:52:53PM +0200, Philipp T?lke wrote:
> > Marcel Linden wrote:
> > >
> Um... I haven't tried this out, but, isn't the deal with Do { foo }
> that it sends command "foo" to FVWM for interpretation?
Yes it is.
I've updated the man
On Tue, Jun 07, 2005 at 10:52:53PM +0200, Philipp T?lke wrote:
> Marcel Linden wrote:
> >
> > Exactly that is the point. Because & sends a task to the background, I
> > exspected that fvwmscript would wait if I don't append &. But it doesn't.
Um... I haven't tried this out, but, isn't the deal w
Marcel Linden wrote:
>>>The script invokes xcalc with & at the end. Because of this I think it
>>>should wait until the program returns.
>>
>>The "&" usually sends a task to the background. Have you tried this without
>>the "&"?
>
> Exactly that is the point. Because & sends a task to the backg
On Tue, 07 Jun 2005 21:44:50 +0200
Philipp Tölke <[EMAIL PROTECTED]> wrote:
> > The script invokes xcalc with & at the end. Because of this I think it
> > should wait until the program returns.
>
> The "&" usually sends a task to the background. Have you tried this without
> the "&"?
Exactly t
Hello,
when I want to execute an external program in a self-written script fvwmscript
doesn't wait until
this external program returns. But in the documentation of fvwmScript is
following example:
If $ToDo=={Open xcalc} Then
Do {Exec xcalc &} # List of instructions
Else
Begin
Do {Exec killall
