alanw@microsoft.UUCP (Alan Whitney) (08/11/83)
It was stated that ANSI does not define a control sequence for
a dim character rendition. That is not the case. \E[2m should
give ``Faint, decreased intensity or secondary color'' on terminals
which support it (my Z-29 does).
Alan Whitney
Microsoft Corp.
{decvax,fluke,uw-beaver}!microsoft!alanwchris@umcp-cs.UUCP (08/11/83)
It figures. In my windows library I used "bo" and "be" for bold and
bold-end, "ws" and "we" for wink (==blink) start and end.
Now, if Berkeley doesn't document their stuff, how do they expect
people to write compatible code?
- Chris
--
In-Real-Life: Chris Torek, Univ of MD Comp Sci
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!chris
CSNet: chris@umcp-cs ARPA: chris.umcp-cs@UDel-Relayandrew@orca.UUCP (Andrew Klossner) (08/17/83)
The ul(1) program included with 4.1aBSD Unix uses some undocumented
TERMCAP fields to provide a variety of character attributes,
particularly including boldface. Since ul is called by man(1) to
present a manual page with appropriate terminal-dependent characters,
this can result in boldface characters instead of reverse video for
program synopses, emphasized words, etc. The resulting display can be
highly readable.
The complete list of ul's TERMCAP fields for character attributes is:
so -- enter stand out mode (normally reverse video)
se -- exit stand out mode
us -- enter underline mode
ue -- exit underline mode
mh -- enter dim mode
md -- enter bold mode
mr -- enter reverse mode
me -- turn off all attributes, normal mode
uc -- underscore a single character
The following line will provide fullblown character attributes for a
terminal which uses the ANSI escape sequences:
:md=\E[1m:me=\E[m:mr=\E[7m:se=\E[m:so=\E[7m:ue=\E[m:ul:us=\E[4m:
(ANSI doesn't define "dim mode".)
This works for the Ann Arbor Ambassador and the VT-102. I suspect that
it might work with the new Teletypes.
-- Andrew Klossner (decvax!tektronix!tekecs!andrew) [UUCP]
(andrew.tektronix@rand-relay) [ARPA]