On 04/07/2026 21:55, Hans-Bernhard Bröker via Cygwin wrote:
Because it's not --- not undocumented, that is. Manpage search can't
seem to find it, but it _is_ there.
Just search for '==' instead, then go one paragraph down.
I suspected the same and did exactly that, but I must be in a different
parallel universe to you ;-)
$ bash --version
GNU bash, version 5.2.21(1)-release (x86_64-pc-cygwin)
This is everything after '==' in the CONDITIONAL EXPRESSIONS section for
me, up to the following section... am I missing some man page updates?
---------------------------------- 8< ----------------------------------
string1 == string2
string1 = string2
True if the strings are equal. = should be used with the
test command for POSIX conformance. When used with the [[ command, this
performs pattern
matching as described above (Compound Commands).
string1 != string2
True if the strings are not equal.
string1 < string2
True if string1 sorts before string2 lexicographically.
string1 > string2
True if string1 sorts after string2 lexicographically.
arg1 OP arg2
OP is one of -eq, -ne, -lt, -le, -gt, or -ge. These
arithmetic binary operators return true if arg1 is equal to, not equal
to, less than, less
than or equal to, greater than, or greater than or equal to
arg2, respectively. Arg1 and arg2 may be positive or negative
integers. When used
with the [[ command, Arg1 and Arg2 are evaluated as
arithmetic expressions (see ARITHMETIC EVALUATION above).
SIMPLE COMMAND EXPANSION
---------------------------------- 8< ----------------------------------
Regards,
Scott
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
