| /src/contrib/tcsh/ |
| H A D | tw.color.c | 59 static Variable variables[] = { variable
90 #define nvariables (sizeof(variables)/sizeof(variables[0]))
226 variables[i].color = variables[i].defaultcolor; in init()
309 makecolor(&c, fg, bg, &variables[map[i]].color); in parseLSCOLORS()
380 if ((Char)variables[i].variable[0] == (v[0] & CHAR) && in parseLS_COLORS()
381 (Char)variables[i].variable[1] == (v[1] & CHAR)) in parseLS_COLORS()
385 getstring(&c, &v, &variables[i].color, ':'); in parseLS_COLORS()
429 Str *colorp = &variables[VFile].color; in print_color()
434 colorp = &variables[VDir].color; in print_color()
442 if (variables[i].suffix != NOS && in print_color()
[all …]
|
| H A D | NewThings | 5 * %$variables are now expanded in the prompt.
26 * $HOSTTYPE is going away. New variables $OSTYPE, $MACHTYPE, $VENDOR similar
38 * set -r makes variables readonly
47 * Imported environment variables are not globbed.
50 * expand variables expands arrays too (but not array elements yet).
55 * shift, left operators update variables correctly.
78 * tcsh now mirrors correctly all exported csh variables [term=TERM,path=PATH
103 * multiple : modifiers in variables and ! escapes. Things like:
136 * shell variables in paths expand correctly.
|
| /src/stand/uboot/ |
| H A D | help.uboot | 3 # Tubenv DShow or import U-Boot environment variables
7 Display U-Boot environment variables, or import them into the
16 variables are imported. Each variable is prefixed with "uboot."
17 to avoid any possible conflicts with loader or kernel variables.
25 variables are shown.
|
| /src/contrib/bmake/unit-tests/ |
| H A D | posix1.exp | 11 Local variables
16 Directory and filename parts of local variables
51 Local variables
56 Directory and filename parts of local variables
97 Local variables
102 Directory and filename parts of local variables
144 Local variables
149 Directory and filename parts of local variables
|
| H A D | depsrc.exp | 1 : 'Undefined variables are expanded directly in the dependency'
3 : 'This is in contrast to local variables such as ${.TARGET}.'
|
| H A D | directive-for-errors.exp | 8 make: directive-for-errors.mk:52: Missing iteration variables in .for loop
9 …e: directive-for-errors.mk:64: Wrong number of words (5) in .for substitution list with 3 variables
|
| /src/contrib/file/magic/Magdir/ |
| H A D | arm | 12 # display name+variables+flags for common object formatted files
21 # display name+variables+flags for common object formatted files
30 # display name+variables+flags for common object formatted files
39 # display name+variables+flags for common object formatted files
48 # display name+variables+flags for common object formatted files
57 # display name+variables+flags for common object formatted files
|
| /src/contrib/pam-krb5/m4/ |
| H A D | lib-helper.m4 | 1 dnl Helper functions to manage compiler variables.
5 dnl CPPFLAGS, LDFLAGS, and LIBS shell substitution variables. Most of them
6 dnl take as one of the arguments the prefix string to use for variables, which
27 dnl To use these macros, pass the prefix string used for the variables as the
49 dnl Given _root, _libdir, and _includedir variables set for a library (set by
50 dnl RRA_LIB_HELPER_WITH*), set the LDFLAGS and CPPFLAGS variables for that
79 dnl Initialize the variables used by a library probe and set the appropriate
80 dnl ones as substitution variables. Takes the library variable prefix as its
94 dnl Unset all of the variables used by a library probe. Used with the
104 dnl Third argument is the variable prefix. The variables set are used by
[all …]
|
| /src/tools/build/options/ |
| H A D | INIT_ALL | 1 Control default initialization of stack variables in C and C++ code.
10 Do not initialize stack variables (standard C/C++ behavior).
12 Build the base system or kernel with stack variables initialized to
16 Build the base system or kernel with stack variables initialized
|
| /src/contrib/ntp/sntp/m4/ |
| H A D | ntp_cacheversion.m4 | 5 # cache variables to avoid using results cached with a script that
9 # all _cv_ variables only makes sense immediately after loading, before
18 # the children can rely on the parent having cleared any cache variables
75 # Do we flush all variables or exclude others' version stamps?
79 # Clear all *_cv_* variables including our child subdirs'
80 # ntp_cv_*_cache_version variables. This prevents subdir
92 # Clear all *_cv_* variables sparing the version stamps
|
| /src/crypto/heimdal/lib/hx509/ |
| H A D | sel-gram.y | 63 %type <expr> variable variables
107 variable: '%' '{' variables '}' { $$ = $3; }
110 variables: IDENTIFIER '.' variables {
|
| /src/contrib/byacc/ |
| H A D | NOTES | 2 use exactly six register variables is that Berkeley Yacc was
3 developed on a VAX using PCC. PCC placed at most six variables
5 variables most belonged in registers. Changes in machines and
|
| /src/usr.bin/mail/ |
| H A D | vars.c | 56 vp->v_link = variables[h]; in assign()
57 variables[h] = vp; in assign()
121 for (vp = variables[hash(name)]; vp != NULL; vp = vp->v_link) in lookup()
|
| H A D | cmd3.c | 363 for (vp = variables[h]; vp != NULL; vp = vp->v_link) in set()
367 for (vp = variables[h]; vp != NULL; vp = vp->v_link) in set()
419 if (vp2 == variables[h]) { in unset()
420 variables[h] = variables[h]->v_link; in unset()
426 for (vp = variables[h]; vp->v_link != vp2; vp = vp->v_link) in unset()
|
| /src/contrib/unbound/ |
| H A D | README-Travis.md | 69 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
73 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
94 …variables `ANDROID_NDK_ROOT` and `ANDROID_SDK_ROOT`. This is an important step because the NDK and…
120 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
122 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
185 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
189 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
221 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
223 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
|
| /src/contrib/ldns/ |
| H A D | README-Travis.md | 65 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
69 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
90 …variables `ANDROID_NDK_ROOT` and `ANDROID_SDK_ROOT`. This is an important step because the NDK and…
116 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
118 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
183 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
187 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
219 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
221 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
|
| /src/contrib/ntp/ntpq/ |
| H A D | ntpq.texi | 59 The description on this page is for the NTPv4 variables.
61 …led using command line arguments. Requests to read and write arbitrary variables can be assembled…
134 The @code{addvars} command allows variables and optional values
138 The @code{rmvars} command can be used to remove individual variables
140 while the @code{clearlist} command removes all variables from the list.
201 Association IDs are used to identify system, peer and clock variables.
202 System variables are assigned an association ID of zero and system name space,
252 Display a list of @ref{clock,,clock variables} for those associations supporting a reference clock.
428 Display the specified variables.
430 the variables are from the @ref{system, system variables} name space,
[all …]
|
| H A D | ntpq-opts.def | 148 variables can be assembled, with raw and pretty-printed output
247 in requests to the server to read variables.
258 command allows variables and their optional values to be added to
264 command can be used to remove individual variables from the list,
267 command removes all variables from the
271 command displays the current list of optional variables.
293 variables which are recognized by
414 Association ids are used to identify system, peer and clock variables.
415 System variables are assigned an association id of zero and system name
458 Display all clock variables in the variable list for those associations
[all …]
|
| H A D | invoke-ntpq.texi | 23 variables can be assembled, with raw and pretty-printed output
122 in requests to the server to read variables.
133 command allows variables and their optional values to be added to
139 command can be used to remove individual variables from the list,
142 command removes all variables from the
146 command displays the current list of optional variables.
168 variables which are recognized by
289 Association ids are used to identify system, peer and clock variables.
290 System variables are assigned an association id of zero and system name
337 Display all clock variables in the variable list for those associations
[all …]
|
| /src/crypto/openssl/doc/man7/ |
| H A D | des_modes.pod | 65 The use of different starting variables prevents the same plaintext
91 The chaining operation makes the ciphertext variables dependent on the
92 current and all preceding variables and therefore j-bit variables are
97 The use of different starting variables prevents the same plaintext
117 An error will affect the current and the following ciphertext variables.
145 The use of different start variables values prevents the same
|
| /src/crypto/openssl/providers/implementations/exchange/ |
| H A D | build.info | 1 # We make separate GOAL variables for each algorithm, to make it easy to
16 # Now that we have defined all the arch specific variables, use the
|
| /src/contrib/llvm-project/lldb/source/Plugins/Platform/QemuUser/ |
| H A D | PlatformQemuUserProperties.td | 19 Desc<"Extra variables to add to the emulator environment.">;
23 Desc<"Extra variables to add to emulated target environment.">;
|
| /src/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | TargetCXXABI.def | 42 /// - guard variables are smaller;
59 /// - guard variables,
82 /// - guard variables are smaller.
97 /// - guard variables are 32-bit on wasm32, as in ARM;
98 /// - unused bits of guard variables are reserved, as in ARM;
|
| /src/crypto/openssl/ |
| H A D | NOTES-ANSI.md | 19 variables:
26 variables:
|
| /src/crypto/openssl/providers/implementations/ciphers/ |
| H A D | build.info | 1 # We make separate GOAL variables for each algorithm, to make it easy to
6 # variables already now, to switch the non-FIPSable TDES to legacy if needed.
61 # Now that we have defined all the arch specific variables, use the
79 # Now that we have defined all the arch specific variables, use the
|