Path: utzoo!utgpu!watserv1!ria!ria.ccs.uwo.ca!clipper From: clipper@det.csd.uwo.ca (Khun Yee Fung) Newsgroups: comp.sources.d Subject: Re: Screen 2.0 change Message-ID: Date: 22 Mar 91 15:11:45 GMT References: <1991Mar19.164204.21361@eci386.uucp> <2921@kraftbus.cs.tu-berlin.de> <2933@kraftbus.cs.tu-berlin.de> Sender: news@ria.ccs.uwo.ca Organization: The University of Western Ontario, C.S. Dept Lines: 33 In-reply-to: net@opal.cs.tu-berlin.de's message of 22 Mar 91 09:55:58 GMT >>>>> On 22 Mar 91 09:55:58 GMT, net@opal.cs.tu-berlin.de (Oliver >>>>> Laumann) said: Oliver> Suppose you start screen on a terminal that supports the Oliver> "blinking" attribute. In this case screen puts a capability Oliver> for "blinking" into the TERMCAP environment variable of the Oliver> programs running under control of screen. Oliver> Now suppose you detach your screen session and resume it on a later Oliver> point in time on a terminal that doesn't have this capability. Yes, I understand that. I wasn't thinking about a general solution. In fact, what I was thinking is a sort of approximation solution. That is, if the new terminal has fewer features than the old one, too bad, the features that it don't have will get mapped to other things. There will be problems, I know. But, for me, this is safer than to terminate a screen session without really knowing what I was running the last time I detached it. In any case, thank you very much for the program. It is the first program I run after logging in every day. It would be much harder for me to work at home if not for your program. Khun Yee -- ---- Name: Khun Yee Fung Email: clipper@csd.uwo.ca Paper Mail: Department of Computer Science Middlesex College The University of Western Ontario London, Ontario, N6A 5B7 CANADA