Re: case statement: wrong behaviour of the ";;&" operator

[Robert Elz]

    Date:        Sat, 26 Jan 2019 06:30:05 +0100
    From:        Norman Krebs <norman.krebs@kohnos.net>
    Message-ID:  <e6578b72-4c3d-8f57-b627-391986458695@kohnos.net>


  |     Following the man page, the ';;&' operator should cause testing the 
_next_
  |     pattern: '2)' only and not _all_ following patterns.

Badly worded manual.   What it means is "pretend this match didn't happen,
even though the command list has been executed, and continue scanning
the patterns in the case statement looking for another match, then do its
list, and after that, whatever its terminating operator says to do".   But that
is quite a mouthfull ...

kre