| /freebsd-14.2/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()
434 colorp = &variables[VDir].color; in print_color()
442 if (variables[i].suffix != NOS && in print_color()
443 (Char)variables[i].suffix == suffix) { in print_color()
444 colorp = &variables[i].color; in print_color()
460 put_color(&variables[VLeft].color); in print_color()
462 put_color(&variables[VRight].color); in print_color()
476 if (0 < variables[VEnd].color.len) in print_with_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.
|
| /freebsd-14.2/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.
|
| /freebsd-14.2/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" line 52: no iteration variables in for
9 …ective-for-errors.mk" line 64: Wrong number of words (5) in .for substitution list with 3 variables
|
| /freebsd-14.2/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
|
| H A D | hitachi-sh | 18 # use big endian variant of subroutine to display name+variables+flags
27 # display name+variables+flags for common object formatted files
|
| /freebsd-14.2/crypto/heimdal/lib/hx509/ |
| H A D | sel-gram.y | 63 %type <expr> variable variables
107 variable: '%' '{' variables '}' { $$ = $3; }
110 variables: IDENTIFIER '.' variables {
|
| /freebsd-14.2/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
|
| /freebsd-14.2/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
|
| /freebsd-14.2/usr.bin/mail/ |
| H A D | vars.c | 62 vp->v_link = variables[h]; in assign()
63 variables[h] = vp; in assign()
127 for (vp = variables[hash(name)]; vp != NULL; vp = vp->v_link) in lookup()
|
| H A D | cmd3.c | 369 for (vp = variables[h]; vp != NULL; vp = vp->v_link) in set()
373 for (vp = variables[h]; vp != NULL; vp = vp->v_link) in set()
425 if (vp2 == variables[h]) { in unset()
426 variables[h] = variables[h]->v_link; in unset()
432 for (vp = variables[h]; vp->v_link != vp2; vp = vp->v_link) in unset()
|
| /freebsd-14.2/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…
|
| /freebsd-14.2/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…
|
| /freebsd-14.2/contrib/ntp/ntpq/ |
| H A D | ntpq.texi | 59 The description on this page is for the NTPv4 variables.
134 The @code{addvars} command allows variables and optional values
428 Display the specified variables.
430 the variables are from the @ref{system, system variables} name space,
434 all operative variables in the name space are displayed.
457 Write the specified variables.
458 If the @code{@kbd{assocID}} is zero, the variables are from the
460 @ref{peer, peer variables} name space.
499 Not all variables are displayed in some configurations.
644 The following peer variables appear in the @code{rv} billboard
[all …]
|
| H A D | ntpq-opts.def | 247 in requests to the server to read variables.
267 command removes all variables from the
293 variables which are recognized by
685 Display all system or peer variables.
691 Display the specified system or peer variables.
694 is zero, the variables are from the
770 is zero, the variables are from the
806 The following system variables appear in the
867 additional system variables are displayed,
891 The following peer variables appear in the
[all …]
|
| /freebsd-14.2/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
|
| /freebsd-14.2/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
|
| /freebsd-14.2/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.">;
|
| /freebsd-14.2/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;
|
| /freebsd-14.2/crypto/openssl/providers/implementations/keymgmt/ |
| H A D | build.info | 1 # We make separate GOAL variables for each algorithm, to make it easy to
25 # Now that we have defined all the arch specific variables, use the
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/mtd/partitions/ |
| H A D | u-boot.yaml | 13 Device configuration is stored as a set of environment variables that are
27 Broadcom stores environment variables inside a U-Boot partition. They
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/nvmem/ |
| H A D | brcm,nvram.yaml | 11 variables. It is used for storing device configuration, booting parameters
17 NVRAM variables can be defined as NVMEM device subnodes.
|
| /freebsd-14.2/contrib/libcbor/CMakeModules/ |
| H A D | FindCMocka.cmake | 6 # Read-Only variables:
56 # show the CMOCKA_INCLUDE_DIR and CMOCKA_LIBRARIES variables only in the advanced view
|