Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!brl-tgr!gwyn From: gwyn@brl-tgr.ARPA (Doug Gwyn) Newsgroups: net.emacs,net.info-terms Subject: Re: termcap cs string Message-ID: <2687@brl-tgr.ARPA> Date: Thu, 31-Oct-85 20:40:29 EST Article-I.D.: brl-tgr.2687 Posted: Thu Oct 31 20:40:29 1985 Date-Received: Sat, 2-Nov-85 07:48:57 EST References: <211@mit-eddie.UUCP> <364@graffiti.UUCP> <241@l5.uucp> Organization: Ballistic Research Lab Lines: 24 Xref: watmath net.emacs:1431 net.info-terms:697 > Info-terms people: see net.emacs, where people have been trying to figure > out what "sg#0" means (something special and undocumented?) ... The meaning of "sg#0" is that it is unsafe to do cursor motions while in standout mode. This was supposed to be the rule anyway unless "ms" is specified, but the manual entries were confusing. The result of this confusion is that a termcap entry should use one of the following: { "sg" and no "ms"} => unsafe to move in standout mode { "sg" and "ms"} => safe to move in standout mode {no "sg" and "ms"} => safe to move in standout mode {no "sg" and no "ms"} is interpretation-dependent; don't use this combination (unless there is also no stand-out capability). > ... and what the arguments to the "cs" string are... The top and bottom line numbers of the scrolling region (inclusive, 0 origin). I wish the EMACS implementors would pay attention to "xo" and the initial terminal modes, also. There are a lot of terminals that require DC3/DC1 flow control, and trying to cheat by supplying generous NUL padding is NOT the right solution.