On 1/13/19 8:45 AM, Ilkka Virta wrote:
> On 13.1. 14:37, Andreas Schwab wrote:
>> On Jan 13 2019, Robert Elz wrote:
>>
>>> The pattern
>>> ./$null"$dir"/
>>>
>>> is expanded (parameter expansion) to
>>>
>>> ./@()./
>>>
>>> which does not have a "." immediately after the / and
>>> tus
On 13.1. 14:37, Andreas Schwab wrote:
On Jan 13 2019, Robert Elz wrote:
The pattern
./$null"$dir"/
is expanded (parameter expansion) to
./@()./
which does not have a "." immediately after the / and
tus cannot match any filename (incoludeing ".") which
starts with a '.'
On 1/12/19 6:58 PM, Peng Yu wrote:
>> The bash-4.4 code only worked the way you want it by chance. There was a
> bug that was fixed in January, 2017, the result of
>
>> http://lists.gnu.org/archive/html/bug-bash/2017-01/msg00018.html
>
>> that uncovered the behavior you're complaining about.
>
Date:Sat, 12 Jan 2019 17:58:12 -0600
From:Peng Yu
Message-ID:
| I don't think it is a good idea to introduce such kind of special
| cases. If @() should match an empty string, the least surprising
| definition is that it should match empty string everywhere.
> The bash-4.4 code only worked the way you want it by chance. There was a
bug that was fixed in January, 2017, the result of
> http://lists.gnu.org/archive/html/bug-bash/2017-01/msg00018.html
> that uncovered the behavior you're complaining about.
This only explains where the change of
On 1/12/19 12:17 AM, Peng Yu wrote:
> See the following for the difference. I'd consider the behavior of
> 4.4.23 should be correct.
The bash-4.4 code only worked the way you want it by chance. There was a
bug that was fixed in January, 2017, the result of
