On 4/27/18 10:02 AM, Robert Elz wrote:
> Date: Fri, 27 Apr 2018 15:06:52 +0200
> From: Joerg Schilling <joerg.schill...@fokus.fraunhofer.de>
> Message-ID:
> <5ae3206c.gzrnd81xboh3e0x7%joerg.schill...@fokus.fraunhofer.de>
>
> | Since bash seems to be the only shell that works this way,
>
> Until I changed the NetBSD sh (if that change is retained), yes.
>
> | I would call this a bug.
>
> Then I think it would be also a bug in POSIX (as I think it
> actually specifies this result) and a deficiency - as there
> really needs to be a way to store a pattern in a variable
> such that a pattern-magic character can be treated literally.
>
> I will leave it for Chet to say whether or not he considers this
> to be a bug in bash.
I don't. If a shell variable contains a literal backslash, that backslash
should be treated as an escape character by the pattern matching engine.
This is as the standard specifies.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
