Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!stanford.edu!rutgers!pyrnj!esquire!baumgart From: baumgart@esquire.dpw.com (Steve Baumgarten) Newsgroups: comp.windows.open-look Subject: Re: Help with SunSO OpenWindows 2.0 window manager and Saber C Message-ID: Date: 8 May 91 15:47:56 GMT References: <9105070650.AA2220@cas.org> Sender: news@DPW.COM Organization: Davis Polk & Wardwell Lines: 29 In-reply-to: lwv27@CAS.BITNET's message of 7 May 91 10:50:11 GMT In article <9105070650.AA2220@cas.org> lwv27@CAS.BITNET (Larry W. Virden ext. 2487) writes: I have the following as one line of many within my $HOME/.openwin-menu file: "Saber-C" xsaber & I have tried just xsaber, exec xsaber, and the above. In each case, I see the outline of the primary window, but before any text appears, the windows go away. When I look in the xterm -C window, there is no output. How can one start programs so that stderr type messages appear SOMEWHERE? And of course, how do we find that somewhere :-) . I believe that Saber C can only be started by running it in an xterm window (i.e., typing "xsaber &" by hand), not from an olwm menu. Twm has the same problem, by the way. The Saber manual explains the technical details, but when I was using twm and tried launching it from a twm menu, the exact same thing happened. -- Steve Baumgarten | "New York... when civilization falls apart, Davis Polk & Wardwell | remember, we were way ahead of you." baumgart@esquire.dpw.com | cmcl2!esquire!baumgart | - David Letterman