Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!whuxl!whuxlm!akgua!gatech!seismo!rochester!bullwinkle!uw-beaver!uw-june!wagner
From: wagner@uw-june.UUCP
Newsgroups: net.unix
Subject: Re: Status line entries in termcap
Message-ID: <465@uw-june>
Date: Tue, 25-Feb-86 16:15:01 EST
Article-I.D.: uw-june.465
Posted: Tue Feb 25 16:15:01 1986
Date-Received: Sat, 1-Mar-86 23:19:30 EST
References: <1004@dcl-cs.UUCP>
Organization: U of Washington Computer Science
Lines: 33
Summary: Here's how sysline(1) uses them.

In article <1004@dcl-cs.UUCP>, de@dcl-cs.UUCP (David England) writes:
> Status line entries are used in /etc/termcap but not mentioned in the
> documentation. Does anyone have any info on hs: es: and ts: ?

Well, you can infer what they mean by how sysline(1) uses them.
From what I can tell,

		hs - Has Status line (boolean)
		ts - move To Status line (string)
		fs - return From Status line (string)
		ds - Delete Status line (string)

Sysline checks for the hs field;  if not found, it exits with the message
"No status capability for {termtype}".  Every write to the status line
is preceded by the ts string and followed by the fs string.  When the
program receives the hangup signal, it sends the ds string.
I haven't seen "es" used anywhere.

Incidentally:  sysline uses the file ".syslinelock" as a binary semaphore.
If you want to temporarily stop sysline from updating the status line,
you just have to create this file.  To resume the updates, remove the file.
This is useful when doing rlogin.  If the remote machine is going to run
sysline, you would want to alias rlogin to something like:
'cat < /dev/null > .syslinelock; /usr/ucb/rlogin \!*; rm .syslinelock'

			Dave Wagner
			University of Washington Comp Sci Department
			wagner@washington.arpa
			{ihnp4,decvax,ucbvax}!uw-beaver!wagner

"Music critics are people who can't write, writing about 
 people who can't hear, for people who can't read."
	- Frank Zappa