Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!rutgers!mcnc!duck!spl
From: spl@duck.ncsc.org (Steve Lamont)
Newsgroups: comp.sys.sgi
Subject: Re: What does winopen(3G) do?
Keywords: winopen sgi edge background parent child wsh
Message-ID: <2252@speedy.mcnc.org>
Date: 4 Jun 90 11:02:11 GMT
References: <May.29.20.11.19.1990.700@genesis.rutgers.edu> <8274@odin.corp.sgi.com> <2238@speedy.mcnc.org> <8315@odin.corp.sgi.com>
Sender: daemon@mcnc.org
Distribution: na
Organization: Foo Bar Brewers Cooperative
Lines: 21

In article <8315@odin.corp.sgi.com> wade@fnord.sgi.com (Wade Olsen) writes:
<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.

Hmmm.  I just open another window.  I usually have about ten windows open
anyhow.

							spl (the p stands for
							phorked up...)
--
Steve Lamont, sciViGuy	(919) 248-1120		EMail:	spl@ncsc.org
NCSC (The other one), Box 12889, Research Triangle Park, NC 27709
"It's not a question of whose habitat it is, it's a question of how hard you
hit it."		-Douglas Adams, "Hitchhiker's Guide to the Galaxy"