Lines Matching refs:capability

34 # This is an adaptation of ncurses' termcap/terminfo capability table, which
44 # extension-capability tables, and a section of aliases declarations.
50 # Column 2: terminfo capability name
51 # Column 3: capability type (Boolean, numeric, or string)
52 # Column 4: termcap capability name
55 # Column 7: Lead with `Y' if capability should be emitted in termcap
57 # Column 8: capability description
60 # use the given capability.  This information is not used by the curses library
68 #	K = remove this terminfo capability when translating to standard format
82 # Column 5: capability description (usually an associated terminfo variable)
91 # this, the capability will be treated as unknown and raise a warning from
94 # 2. Alias it.  This is appropriate if the capability has the same meaning
105 # do this, the capability will be ignored on input (though the user will
109 # silently accept the capability, but the curses library proper will never
114 # to eat the capability silently and discard it when doing translations
119 # capability value that it can use to translate it into your output format.
137 # We retain the sgr capability in translation in spite of the fact that neither
158 # We manually specify a (minimum) column width for the capability name
163 # The longest capability names (C variable) is
185 #%The capability name identifies the symbol by which the programmer
188 #%API accesses the capability.
221 #%The description field attempts to convey the capability's semantics.
235 #%parameter of a string capability;
666 # terminfo equivalents.  The rs capability is specially translated to terminfo
669 # The ug capability is thrown away, but assumed to be whatever sg is if the
696 # GNU termcap *does* include the following extended capability,  Only the
712 # The `ko' capability is translated by special code.  It should contain a
716 # The `ma' capability was a 4.0BSD feature used by vi version 2.
751 # mytinfo described this as a termcap capability, but it is not listed in the