| /openbsd-src/lib/libcurses/ |
| H A D | user_caps.5 | 56 user_caps \- user-defined terminfo capabilities
63 capabilities designed for the SVr2 terminal database in 1984,
68 to the tables of boolean, numeric and string capabilities.
86 The format cannot represent very large numeric capabilities,
95 While ncurses' repertoire of predefined capabilities is closest to Solaris,
104 which lists the different terminal capabilities.
108 The text-file used in ncurses for terminal capabilities includes
110 For example, ncurses supports these capabilities in each configuration:
126 The memory lock/unlock capabilities were included because they were used
136 (or required them to reuse existing capabilities as a workaround).
[all …]
|
| H A D | term.5 | 136 The capabilities in the
185 Boolean capabilities are either 1 or 0 (true or false)
205 It contains all of the values of string capabilities referenced in
216 Each system uses a predefined set of boolean, number or string capabilities.
220 allowing users to define capabilities which are loaded at runtime.
233 count of extended boolean capabilities
236 count of extended numeric capabilities
239 count of extended string capabilities
253 for the extended capabilities in the same order as the header information.
255 The extended string table contains values for string capabilities.
[all …]
|
| H A D | terminfo.5 | 80 describes terminals by giving a set of capabilities which they
164 .SS Terminfo Capabilities Syntax
173 Boolean capabilities are true when present, false when absent.
174 There is no explicit value for boolean capabilities.
176 Numeric capabilities have a \*(``#\*('' following the name,
179 String capabilities have a \*(``=\*('' following the name,
182 String capabilities can be split into multiple lines,
200 The capabilities given before
205 If there are multiple \fBuse\fP capabilities, they are merged in reverse order.
209 Capabilities give
[all...] |
| H A D | Caps | 45 # This file has three major sections; a standard-capabilities table, two
101 # to do this -- the capabilities in that one, and their order, have been
154 # Emacs only, we'll probably elide out some BSD-only capabilities in order
155 # to buy space for non-essentials Emacs is still using. Capabilities high
160 # STANDARD CAPABILITIES
162 #%The following is a complete table of the capabilities included in a
178 #%capability name (some capabilities are new, and have names which termcap
209 #% These are the boolean capabilities:
259 #%These are the numeric capabilities:
289 #%The following numeric capabilities are present in the SVr4.0 term structure,
[all …]
|
| H A D | term_variables.3 | 121 the long and short names of terminfo capabilities,
122 as well as the corresponding names for termcap capabilities.
132 These are the short names for terminfo capabilities:
160 These symbols provide a faster method of accessing terminfo capabilities
|
| H A D | curs_print.3 | 41 This function uses the \fBmc5p\fP or \fBmc4\fP and \fBmc5\fP capabilities,
60 Capabilities for printer redirection do not exist.
71 Padding in the \fBmc5p\fP, \fBmc4\fP and \fBmc5\fP capabilities will not be
|
| H A D | capdefaults.c | 41 * Compute obsolete capabilities. The reason this is an include file is
56 /* current (4.4BSD) capabilities marked obsolete */
63 /* current (4.4BSD) capabilities not obsolete */
80 /* totally obsolete capabilities */
|
| H A D | Caps-ncurses | 35 # TERMINFO EXTENSION CAPABILITIES
38 # specific "Caps" files). The section describes what capabilities need to be
113 # The places in the box[12] capabilities correspond to acsc characters, here is
184 # The key_smap_in[6789] and key_smap_out[6789] capabilities aren't described in
195 # Undocumented capabilities end here
210 # Undocumented capabilities end here.
212 # The IBM docs say these capabilities are for table-drawing, and are
237 # nonstandard capabilities. Its signature is the KM capability, used to name
334 # Some others are identical to SVr4/XPG4 capabilities, in particular:
338 # This is a table of ncurses user-definable capabilities which applications
[all …]
|
| H A D | terminfo.3 | 130 capabilities, such as programming function keys.
150 terminal capabilities either directly (via header definitions),
264 It maintains only one copy of a given terminal's capabilities in memory.
266 \fBsetupterm\fP allocates new storage for each set of terminal capabilities.
299 most terminal capabilities require no more than one or two parameters.
396 \fIcapname\fP code in the capabilities section of \fBterminfo\fP(\*n).
724 However, only a few terminfo capabilities use string parameters
727 The ncurses library checks usage of these capabilities,
732 The \fBtput\fR(1) program checks its use of these capabilities with a table,
|
| /openbsd-src/usr.bin/tic/ |
| H A D | tic.1 | 149 tells \fBtic\fP to retain commented-out capabilities rather than discarding
151 Capabilities are commented by prefixing them with a period.
162 Capabilities
179 capabilities with more than one delay or with delays before the end of
195 \fBtic\fP checks string capabilities to ensure that those with parameters
197 It does this check only for the predefined string capabilities;
246 a number of assumptions about the defaults of string capabilities
250 to use obsolete termcap capabilities to deduce correct values.
252 normally suppresses output of obsolete termcap capabilities such as \fBbs\fP.
254 obsolete capabilities.
[all …]
|
| H A D | captoinfo.1 | 46 Termcap \fBtc\fP capabilities are translated directly to terminfo
47 \fBuse\fP capabilities.
75 .SH TRANSLATIONS FROM NONSTANDARD CAPABILITIES
76 Some obsolete nonstandard capabilities will automatically be translated
77 into standard (SVr4/XSI Curses) terminfo capabilities by \fBcaptoinfo\fP.
120 XENIX termcap also used to have a set of extension capabilities
155 If the single-line capabilities occur in an entry, they will automatically
157 The double-line capabilities and
182 capabilities \fBmeml\fP (memory lock) and \fBmemu\fP (memory unlock).
|
| /openbsd-src/usr.bin/infocmp/ |
| H A D | infocmp.1 | 118 \fIabsent\fP and \fIcancelled\fP capabilities.
132 Missing capabilities are ignored.
144 Normally only the conventional capabilities are shown.
146 capabilities (names prefixed with \*(``OT\*('').
161 \fB\-r\fP/when using \fB\-C\fP, put out all capabilities in \fBtermcap\fP form
194 \fBterminfo\fP capabilities will be translated; only those variables which were
197 will take off this restriction, allowing all capabilities to be output in
206 all capabilities are output.
257 terminfo compiler \fBtic\fP does a left-to-right scan of the capabilities,
259 capabilities will produce different results depending on the order that the
[all …]
|
| /openbsd-src/usr.sbin/dvmrpd/ |
| H A D | probe.c | 80 u_int8_t capabilities, char *buf, u_int16_t len) in recv_probe() argument
98 nbr->capabilities = capabilities; in recv_probe()
104 if ((nbr->gen_id != gen_id) || (nbr->capabilities != capabilities)) { in recv_probe()
108 nbr->capabilities = capabilities; in recv_probe()
|
| /openbsd-src/usr.bin/tput/ |
| H A D | tput.1 | 62 values of terminal-dependent capabilities and information available to
87 For a complete list of capabilities
93 capabilities must be passed to \fBtput\fP from the standard input
100 Because some capabilities may use
126 \fBtput\fP uses several capabilities to perform these special functions.
135 Only a few terminal capabilities require string parameters;
248 On the other hand, \fBtset\fP's repertoire of terminal capabilities for
277 tput treats certain terminfo capabilities specially:
356 This example shows \fBtput\fP processing several capabilities
444 the capabilities whic
[all...] |
| /openbsd-src/usr.sbin/radiusd/ |
| H A D | radiusd_local.h | 81 uint32_t capabilities; member
178 ((_m)->capabilities & RADIUSD_MODULE_CAP_USERPASS) != 0)
181 ((_m)->capabilities & RADIUSD_MODULE_CAP_ACCSREQ) != 0)
184 ((_m)->capabilities & RADIUSD_MODULE_CAP_ACCTREQ) != 0)
187 ((_m)->capabilities & RADIUSD_MODULE_CAP_REQDECO) != 0)
190 ((_m)->capabilities & RADIUSD_MODULE_CAP_RESDECO) != 0)
193 ((_m)->capabilities & RADIUSD_MODULE_CAP_NEXTRES) != 0)
|
| /openbsd-src/share/termtypes/ |
| H A D | termcap.5 | 48 by giving a set of capabilities that they have and by describing
91 .Sh CAPABILITIES
105 capabilities have no
108 or are subsumed by other capabilities.
424 .Ss Types of Capabilities
425 Capabilities in
427 are of three types: Boolean capabilities,
429 numeric capabilities,
431 and string capabilities,
434 All capabilities have two-letter codes.
[all …]
|
| /openbsd-src/share/man/man4/ |
| H A D | ipmi.4 | 91 .Sh SENSOR DATA RECORDS & CAPABILITIES COMMANDS
95 different event generation capabilities.
98 and automatically configure itself to the platform's capabilities.
100 Information that describes the platform management capabilities
102 Capabilities Commands and Sensor Data Records (SDRs).
103 Capabilities commands are commands within the IPMI command sets that return
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | ThreadSafetyAnalysis.rst | 96 Basic Concepts: Capabilities
100 *capabilities*. A resource is either a data member, or a function/method
105 Capabilities are associated with named C++ objects which declare specific
119 capabilities (e.g. the set of mutexes that it has locked.) These act like keys
124 exact mechanism used to acquire and release capabilities; it assumes that the
128 The set of capabilities that are actually held by a given thread at a given
132 and describes the set of capabilities that are statically known to be held, or
134 approximation of the full set of capabilities that will actually held by a
192 capabilities. More than one capability may be specified. The capabilities
287 the caller must *not* hold the given capabilities. This annotation is
[all …]
|
| /openbsd-src/gnu/llvm/llvm/lib/Target/SPIRV/ |
| H A D | SPIRVModuleAnalysis.h | 68 // Remove a list of capabilities from dedupedCaps and add them to AllCaps,
69 // recursing through their implicitly declared capabilities too.
88 // Add a list of capabilities, ensuring AllCaps captures all the implicitly
89 // declared capabilities, and MinimalCaps has the minimal set of required
90 // capabilities (so all implicitly declared ones are removed).
107 // Add the given capabilities to available and all their implicitly defined
108 // capabilities too.
|
| /openbsd-src/lib/libc/gen/ |
| H A D | cgetent.3 | 325 The remaining non-empty capabilities describe a set of (name, value)
384 Typeless capabilities are typically used to denote boolean objects with
398 capabilities may interpolate records which also contain
400 capabilities and more than one
427 capabilities can be used to generate variations of other databases and
428 records by either adding new capabilities, overriding definitions with new
431 capabilities.
|
| /openbsd-src/sys/dev/pci/drm/amd/display/include/ |
| H A D | ddc_service_types.h | 78 capabilities going INTO SINK DEVICE (stream capabilities)
100 capabilities going OUT OF SOURCE DEVICE (link capabilities)
|
| /openbsd-src/share/man/man4/man4.amd64/ |
| H A D | vmm.4 | 64 driver requires suitable host CPU capabilities in order to provide
69 capabilities and nested or extended paging capabilities to be
|
| /openbsd-src/gnu/llvm/llvm/utils/lit/lit/ |
| H A D | ProgressBar.py | 95 assumed to be a dumb terminal (i.e., have no capabilities).
101 # If the stream isn't a tty, then assume it has no capabilities.
105 # terminal has no capabilities.
109 # Look up numeric capabilities.
114 # Look up string capabilities.
142 # String capabilities can include "delays" of the form "$<2>".
|
| /openbsd-src/usr.bin/getcap/ |
| H A D | getcap.1 | 52 capabilities database (i.e. literally), use a
61 capabilities database, use a
66 Use this for querying capabilities with non-standard types or
|
| /openbsd-src/gnu/llvm/llvm/lib/Target/SPIRV/MCTargetDesc/ |
| H A D | SPIRVBaseInfo.cpp | 10 // versioning/capabilities/extensions getters for symbolic/named operands used
121 CapabilityList Capabilities; in getSymbolicOperandCapabilities() local
124 Capabilities.push_back( in getSymbolicOperandCapabilities()
129 return Capabilities; in getSymbolicOperandCapabilities()
|