Lines Matching full:capability

107 If a capability is defined for only one of the
108 terminals, the value returned depends on the type of the capability:
121 produces a list of each capability that is \fIdifferent\fP
123 Each item in the list shows \*(``:\*('' after the capability name,
124 followed by the capability values, separated by a comma.
127 produces a list of each capability that is \fIcommon\fP between
130 Each item in the list shows \*(``=\*('' after the capability name,
131 followed by the capability value.
138 produces a list of each capability that is in \fInone\fP of the given entries.
139 Each item in the list shows \*(``!\*('' before the capability name.
155 \-I	use \fIterminfo\fP capability codes
156 \-L	use \*(``long\*('' capability names
157 \-C	use \fItermcap\fP capability codes
202 Note that because padding is collected to the beginning of the capability, not
207 a \fBterminfo\fP string capability into an equivalent \fBtermcap\fP format.
250 A capability will be printed with an at-sign (@) if it no longer exists in the
254 A capability's value will be printed if the value in the first
258 capability gives a different value for the capability than that in the
270 Alternatively, specifying a capability \fIafter\fP a \fBuse=\fP entry that
271 contains that capability will cause the second specification to be ignored.
327 TERMTYPE structure (the terminal capability structure in the \fB<term.h>\fP).
340 TERMTYPE structure (the terminal capability structure in the \fB<term.h>\fP).
383 of the capability name, followed by a colon and space, followed by a printable
384 expansion of the capability string with sections matching recognized actions