ncurses/include/Caps.hpux11

12 # The above copyright notice and this permission notice shall be included in #
24 # holders shall not be used in advertising or otherwise to promote the sale, #
54 # Column 7: Lead with `Y' if capability should be emitted in termcap
68 # The important codes are C and E.  A cap with C or E should be preserved in
77 # Column 2: name to be aliased
79 #           should be discarded with a warning message.
90 # this, the capability will be treated as unknown and raise a warning from
99 # carefully chosen to be SVr4-binary-compatible when they're written out
100 # as a terminfo object, and breaking this would be bad.  It's up the ncurses
104 # do this, the capability will be ignored on input (though the user will
109 # see it (because it won't be written out as part of the terminfo object
126 # Machines with IBM PC-like keyboards want to be able to define the following
129 # the set of keys the `joe' editor will be upset if it can't see.  So don't
130 # trim those out of the set to be translated to termcap, or various users of
139 # to be older types that don't use up a lot of string space on function keys.
144 # optimizer in BSD curses didn't use them.  This omission seems to be the
148 # It would be nice to keep f11 and f12 for Emacs use, but a couple of termcap
168 #%Whenever possible, capnames are chosen to be the same as or similar to
188 #%indicates that padding may be specified
223 memory_above			da	bool	da	-	-	YBCG-	display may be retained above the screen
224 memory_below			db	bool	db	-	-	YB-GE	display may be retained below the screen
228 status_line_esc_ok		eslok	bool	es	-	-	YB-G-	escape can be used on the status line
280 no_color_video			ncv	num	NC	-	-	-----	video attributes that cannot be used with colors
753 #%entries use these, they may not be binary-compatible with System V terminfo
782 # past it should be ignored (not written out) when dumping terminfo objects. It
811 # The ug capability is thrown away, but assumed to be whatever sg is if the
845 # clash with terminfo names in ways that cannot be resolved by type
901 # be resolved by a type check.  The descriptions are guesses from what was
911 # SR clashes with a terminfo name; this ambiguity cannot be resolved by a type
953 # strings that happen to be numerics.  There's awk code in parametrized.sh
974 # what capabilities need to be squeezed out to get down to the XSI Curses