Issue with Bash RegEx Handling

Annihilannic annihilannic@hotmail.com
Sun Jul 5 23:35:58 GMT 2026


On 06/07/2026 00:45, ASSI via Cygwin wrote:
> Annihilannic via Cygwin writes:
>> I suspected the same and did exactly that, but I must be in a different
>> parallel universe to you ;-)
> No, you are just not following the instructions.  The paragraph you'll
> find is this (quotest with the paragraphs above an below for clarity):

Indeed... since I was preconceived to find it in the canonical list of 
expressions in the CONDITIONAL EXPRESSIONS section rather than embedded 
deep in a paragraph under SHELL GRAMMAR / Compound Commands... thanks 
for saving my sanity.

On 06/07/2026 03:17, Hans-Bernhard Bröker via Cygwin wrote:
 > 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.

A case of WYSINQWYG!  Thanks.  I had already found the info in 'info', 
per my original post, but it is never my first port of call due to its 
horrible and very forgettable navigation, in my opinion.

Regards,
Scott


More information about the Cygwin mailing list