dorner@pequod.cso.uiuc.edu (Steve Dorner) (05/17/89)
When I have multiple copies of Terminal running, quitting one of
them frequently zaps them all. This didn't happen under 0.8.
Does it happen to anyone else, or am I just talented?
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu UUCP: {convex,uunet}!uiucuxc!dorner
IfUMust: (217) 244-1765louie@trantor.umd.edu (Louis A. Mamakos) (05/17/89)
I see this problem too; though so far it seems like I've only noticed it happen when I've got an rlogin running in two windows to the same host. When one exits, the goes with it too. Weird. On another topic, why doesn't the spooling system reverse the pages on the printer on files printed from WriteNow. When printing the release notes, the pages are stacked on the printer in the wrong order. Under 0.8, the (conforming) PostScript files were run through psrv before being printed. Louis A. Mamakos WA3YMH Internet: louie@TRANTOR.UMD.EDU University of Maryland, Computer Science Center - Systems Programming
carlson@mrcnext.cso.uiuc.edu (05/17/89)
I have seen both Terminal and Workspace quit uxexpectely or get garbage pixels occasionally. -------------------- Brad Carlson <carlson@mrcnext.cso.uiuc.edu> or <b-carlson@uiuc.edu> University of Illinos--Micro Resource Center--NeXT guru
tj@wb1.cs.cmu.edu (Cal Thixton) (05/25/89)
In article <1006@garcon.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: >When I have multiple copies of Terminal running, quitting one of >them frequently zaps them all. This didn't happen under 0.8. >Does it happen to anyone else, or am I just talented? >-- >Steve Dorner, U of Illinois Computing Services Office >Internet: s-dorner@uiuc.edu UUCP: {convex,uunet}!uiucuxc!dorner >IfUMust: (217) 244-1765 This problem is fixed and will be in 1.0. Sorry for any inconvenience. morris meyer Software Engineer NeXT OS Group --
dmr@csli.Stanford.EDU (Daniel M. Rosenberg) (05/25/89)
In article <5059@pt.cs.cmu.edu> tj@wb1.cs.cmu.edu (Cal Thixton) writes: >In article <1006@garcon.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: >>When I have multiple copies of Terminal running, quitting one of >>them frequently zaps them all. This didn't happen under 0.8. >This problem is fixed and will be in 1.0. Sorry for any inconvenience. Is there any way these kinds of fixes could be posted to the network or left or anonymous ftp somewhere? Or is there a policy against releasing software between official releases? Thanks for any information *anyone* can provide. -- # Daniel M. Rosenberg // Stanford CSLI // Opinions are my own only. # dmr@csli.stanford.edu // decwrl!csli!dmr // dmr%csli@stanford.bitnet
jasmerb@mist.CS.ORST.EDU (Bryce Jasmer) (05/25/89)
>>In article <1006@garcon.cso.uiuc.edu> (Steve Dorner) writes: >>This problem is fixed and will be in 1.0. Sorry for any inconvenience. >Is there any way these kinds of fixes could be posted to the network >or left or anonymous ftp somewhere? Or is there a policy against releasing >software between official releases? I talked to our local SE about what NeXT's official policy was on distributing patches was while I was setting up the cs.orst.edu ftp archive site. The reply was that NeXT will not distribute patches (period). They figure you can wait until the next release of the OS. I have a directory on the ftp site that has been set up from the start for the purpose of holding official NeXT patches but it looks like it will probably remain empty unless NeXT changes their policy. Bryce Jasmer jasmerb@hobbes.cs.orst.edu (next-ftp@cs.orst.edu)