Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!uwm.edu!rpi!dali!uakari.primate.wisc.edu!dogie.macc.wisc.edu!decwrl!sgi!shinobu!odin!fnord!wade From: wade@fnord.sgi.com (Wade Olsen) Newsgroups: comp.sys.sgi Subject: Re: What does winopen(3G) do? Keywords: winopen sgi edge background parent child wsh Message-ID: <8315@odin.corp.sgi.com> Date: 31 May 90 17:46:23 GMT References: <8274@odin.corp.sgi.com> <2238@speedy.mcnc.org> Sender: news@odin.corp.sgi.com Distribution: na Lines: 14 In article <2238@speedy.mcnc.org> spl@duck.ncsc.org (Steve Lamont) writes: >Pardon my puzzlement, but what are the comparative advantages of forking or >not forking upon winopen()? Graphics programs that don't fork are a pain because they tie up the shell from which they were invoked (i.e. you get no shell prompt until the graphics program exits). You could just remember to run them in background by appending and ampersand to the invocation line, but this leaves a bad taste in my mouth. Wade ++ Wade Olsen, wade@sgi.com, X1023