Home
last modified time | relevance | path

Searched refs:colons (Results 1 – 25 of 33) sorted by relevance

12

/freebsd/usr.bin/bmake/tests/syntax/funny-targets/
H A DMakefile.test5 test1: colons::colons::target
7 colons::colons::target:
H A Dexpected.stdout.11 colons::colons::target
/freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/cmd/jdtrace/
H A DJDTrace.java89 int colons = 0; in applyProbespec() local
92 colons = 3; in applyProbespec()
95 colons = 2; in applyProbespec()
98 colons = 1; in applyProbespec()
103 if (colons > 0) { in applyProbespec()
140 for (int c = 0; c < colons; ++c) { in applyProbespec()
/freebsd/contrib/bmake/unit-tests/
H A Dvar-op-sunsh.mk42 VAR:shoe:shore= echo two-colons
/freebsd/sys/contrib/device-tree/Bindings/
H A D.yamllint24 colons: {max-spaces-before: 0, max-spaces-after: 1}
/freebsd/usr.sbin/iscsid/
H A Discsid.c154 int error, colons = 0; in resolve_addr() local
187 colons++; in resolve_addr()
189 if (colons > 1) { in resolve_addr()
/freebsd/usr.sbin/bsdconfig/networking/include/
H A Dmessages.subr66 …OR! One or more individual segments within the IP address\n(separated by colons) contains one or m…
67 …OR! One or more individual segments within the IP address\n(separated by colons) exceeds the lengt…
68 …s than 3), too\nmany (more than 8), or not enough segments, separated by colons.\n\nInvalid IPv6 A…
/freebsd/usr.bin/sed/tests/
H A Dhanoi.sed15 # towers) and delimited by 4 colons, such that the letters within each field
/freebsd/contrib/libxo/doc/
H A Dfield-roles.rst131 Decorations are typically punctuation marks such as colons,
132 semi-colons, and commas used to decorate the text and make it simpler
H A Doptions.rst176 colons (":") or plus signs ("+"):
/freebsd/contrib/wpa/wpa_supplicant/
H A DREADME-DPP108 separating colons. The channel list includes the possible channels on which the
/freebsd/usr.sbin/bsdconfig/share/media/
H A Dtcpip.subr255 # (separated by colons) contains one or more invalid characters.
259 # allowed within the IP address (separated by colons) but not
263 # (separated by colons) exceeds the length of 4 hex-digits.
266 # colons.
/freebsd/usr.sbin/ctld/
H A Dctld.c635 int error, colons = 0; in parse_addr_port() local
663 colons++; in parse_addr_port()
665 if (colons > 1) { in parse_addr_port()
/freebsd/crypto/openssl/doc/man1/
H A Dopenssl-dgst.pod.in70 Print out the digest in two digit groups separated by colons, only relevant if
H A Dopenssl-ciphers.pod.in115 The cipher list consists of one or more I<cipher strings> separated by colons.
116 Commas or spaces are also acceptable separators but colons are normally used.
H A Dopenssl-ts.pod.in146 per byte, the bytes optionally separated by colons (e.g. 1A:F6:01:... or
/freebsd/crypto/openssl/doc/man7/
H A Dproxy-certificates.pod92 colons between each byte (every second hex digit):
/freebsd/usr.bin/sed/
H A DPOSIX80 by semi-colons, e.g. 'sed -ne '1p;2p;3q' printed the first
/freebsd/contrib/llvm-project/libcxx/include/
H A Dvariant663 // Adding semi-colons in macro expansions helps clang-format to do a better job.
664 // This macro is used to avoid compilation errors due to "stray" semi-colons.
/freebsd/crypto/openssl/Configurations/
H A DREADME.md331 values separated by colons. This use is deprecated. The string form
/freebsd/contrib/sendmail/cf/cf/
H A Dsubmit.cf401 # are colons OK in addresses?
/freebsd/contrib/sendmail/cf/m4/
H A Dproto.m4551 # are colons OK in addresses?
840 dnl R$* < @ $~[ $* : $* > $* $1 < @ $2 $3 > $4 nix colons in addrs
/freebsd/contrib/flex/
H A DONEWS961 - The funky restrictions on when semi-colons could follow the
/freebsd/contrib/expat/
H A DChanges926 XML names; XML names with multiple colons could end up in
/freebsd/contrib/mandoc/
H A DNEWS636 * Fix handling of leading, trailing, and double colons in MANPATH and -m.

12