Path: utzoo!attcan!uunet!mcvax!hp4nl!philmds!nlgvax!tom From: tom@nlgvax.UUCP (Tom van Peer) Newsgroups: comp.windows.news Subject: Re: Fun with forkunix Keywords: &main Message-ID: <155@nlgvax.UUCP> Date: 17 Nov 88 07:42:02 GMT References: <5897@hoptoad.uucp> Reply-To: tom@nlgvax.UUCP (Tom van Peer) Organization: Philips Research Geldrop Lines: 35 In article <5897@hoptoad.uucp> gnu@hoptoad.uucp (John Gilmore) writes: >montnaro@sprite.steinmetz.ge.com (Skip Montanaro) wrote: >> I've been trying to get around a bug in NeWS that makes starting programs >> from user.ps unreliable. (It's bug #1004790. It's been around since NeWS 1.0 >> and is still present in 1.1. I'll send the workaround to anyone interested.) >> The symptom is that when starting programs from user.ps, such as: >> >> (psterm -ls -bg -li 16 -co 80 -sl 128 -C) forkunix >> (emacs) forkunix >> >> sometimes the windows show up, but most times not. > >I believe this is because at the time user.ps runs, the server has not >yet started accepting connections. Let me first state that I don't know about bug #1004790 (so please flame mildly if the following doesn't work). When looking at init.ps I find that &main is run after the server has started. So if you define &main in user.ps and put your forkunixes in there like: /&main { go! % necessarry to get processes running. (psterm -ls -bg -li 16 -co 80 -sl 128 -C) forkunix (emacs) forkunix } def everything should work fine. -- Tom van Peer Nederlands Philips Bedrijven, Dependance Nat. Lab. Building XP Willem Alexanderlaan 7B, 5664 AN Geldrop - The Netherlands. Tel: +31-40-892334 E-mail: mcvax!philmds!nlgvax!tom or tom@pcg.philips.nl