Article View: comp.sources.d
Article #1643Re: Screen 2.0 change
From: Oliver Laumann
Date: Fri, 22 Mar 1991 09:55
Date: Fri, 22 Mar 1991 09:55
18 lines
1424 bytes
1424 bytes
In article <CLIPPER.91Mar21181432@det.csd.uwo.ca> clipper@det.csd.uwo.ca (Khun Yee Fung) writes: > Is there a way to tell screen on the fly that the physical terminal > has changed? No. This wouldn't work in general. Suppose you start screen on a terminal that supports the "blinking" attribute. In this case screen puts a capability for "blinking" into the TERMCAP environment variable of the programs running under control of screen. Now suppose you detach your screen session and resume it on a later point in time on a terminal that doesn't have this capability. What should happen when an application running under screen outputs ^[[5m to set the blinking attribute? The application still thinks this capability is supported, and there is, of course, no way for screen to change the value of $TERMCAP for a child process on the fly. -- Oliver Laumann net@tub.cs.tu-berlin.de net@tub.UUCP net@gnu.ai.mit.edu
Technical Details
Message-ID:
<2933@kraftbus.cs.tu-berlin.de>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!watserv1!watmath!att!pacbell.com!mips!spool.mu.edu!snorkelwacker.mit.edu!ai-lab!opal!netReferences:
<1991Mar19.164204.21361@eci386.uucp> <2921@kraftbus.cs.tu-berlin.de> <CLIPPER.91Mar21181432@det.csd.uwo.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!watserv1!watmath!att!pacbell.com!mips!spool.mu.edu!snorkelwacker.mit.edu!ai-lab!opal!net From: net@opal.cs.tu-berlin.de (Oliver Laumann) Newsgroups: comp.sources.d Subject: Re: Screen 2.0 change Message-ID: <2933@kraftbus.cs.tu-berlin.de> Date: 22 Mar 91 09:55:58 GMT References: <1991Mar19.164204.21361@eci386.uucp> <2921@kraftbus.cs.tu-berlin.de> <CLIPPER.91Mar21181432@det.csd.uwo.ca> Organization: Technical University of Berlin, Germany Lines: 18