The following issue has a resolution that has been APPLIED.
==
http://austingroupbugs.net/view.php?id=1253
==
Reported By:eggert
Assigned
On 24/10/2019 08:16, Robert Elz wrote:
Date:Thu, 24 Oct 2019 06:46:52 +0100
From:Harald van Dijk
Message-ID: <5d23eeba-1ac5-6574-d348-2a8b43f97...@gigawatt.nl>
| This is currently well-defined. We are talking about changing the
| standard to make it
Date:Thu, 24 Oct 2019 06:46:52 +0100
From:Harald van Dijk
Message-ID: <5d23eeba-1ac5-6574-d348-2a8b43f97...@gigawatt.nl>
| This is currently well-defined. We are talking about changing the
| standard to make it unspecified.
I am not sure about the first
Harald van Dijk wrote, on 23 Oct 2019:
>
> On 22/10/2019 09:47, Geoff Clare wrote:
> >Good catch. Since there is no reason for a user or application to
> >escape a slash with a backslash, I see no reason why this shouldn't be
> >made unspecified.
> I wanted to agree with this, especially since
Date:Thu, 24 Oct 2019 09:25:52 +0100
From:Harald van Dijk
Message-ID: <9c38ef54-adf6-9af5-0f98-1f3105526...@gigawatt.nl>
| That is what almost all shells do, but not what POSIX specifies.
Not explicitly perhaps, but it is almost the only way to achieve the
effects
