Issue with Bash RegEx Handling

[Hans-Bernhard Bröker]

Am 05.07.2026 um 05:18 schrieb Keith Thompson via Cygwin:
>>> Firstly, why is =~ completely undocumented in the bash man page?  This
>>> question was my first encounter with the feature.
>> ·
>> 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.
> Searches in man pages are controlled by your pager ($PAGER or
> $MANPAGER).  Your pager might be treating the ~ character specially.
> Try searching for \~= .

It doesn't appear to be the pager --- it's groff translating the ~ to 
some other character.  One which I don't know how to type into the 
search pattern.

What does help for me is overriding the language spec:

     $ LC_ALL=C man bash

and, voila, / finds =~ just fine.

And FWIW, 'info bash' doesn't have that problem, either.