Path: utzoo!mnetor!uunet!husc6!uwvax!rutgers!bellcore!tness7!tness1!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: WorkBench Processes...
Message-ID: <1867@sugar.UUCP>
Date: 20 Apr 88 13:32:30 GMT
References: <386@uvicctr.UUCP> <1837@sugar.UUCP> <467@sas.UUCP>
Distribution: na
Organization: Sugar Land UNIX - Houston, TX
Lines: 18
Summary: Danger, Will Robinson!

In article <467@sas.UUCP>, walker@sas.UUCP (Doug Walker) writes:
> In article <1837@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
> >"click" ... runs a workbench process and waits for it to finish.

> You can also use 'WBRUN' by John Toebes.  It's on one of the Fish disks.
> You don't even have to wait for it to finish:  it starts the process and
> then returns your CLI to you.  Also, you don't even have to have workbench
> loaded to do it.

And how does WBRUN handle cleaning up the WBStartup message? That's why I wait
for it to finish... you need to get that message back and clean up after
yourself.

You don't need workbench loaded to run "click", either, by the way.
-- 
-- Peter da Silva      `-_-'      ...!hoptoad!academ!uhnix1!sugar!peter
-- "Have you hugged your U wolf today?" ...!bellcore!tness1!sugar!peter
-- Disclaimer: These aren't mere opinions, these are *values*.