Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Eduardo A . Bustamante López
On Mon, Aug 13, 2018 at 10:52:20PM -0400, Bize Ma wrote: (...) > That version is not even beta, it is still alpha, are you asking that > everyone should use > non-released (and not yet tested as beta) alpha release ? (...) I didn't say that. My point is that, in the context of bug reports, it's im

Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Bize Ma
2018-08-13 22:09 GMT-04:00 Eduardo A. Bustamante López : > On Mon, Aug 13, 2018 at 09:36:23PM -0400, Bize Ma wrote: > (...) > > Please, do not waste our time in incorrect claims. > > > > Do your homework and test ! > (...) > > > dualbus@ubuntu:~/src/gnu/bash$ bash /tmp/script > 4.4.19(1)-releas

Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Eduardo A . Bustamante López
On Mon, Aug 13, 2018 at 09:36:23PM -0400, Bize Ma wrote: (...) > Please, do not waste our time in incorrect claims. > > Do your homework and test ! (...) Did you test Bash 5.0? Because that's where the current bug fixes are going to. I don't see Chet releasing a new version of 4.4 to fix somethin

Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Bize Ma
2018-08-13 21:16 GMT-04:00 Eduardo Bustamante : > On Mon, Aug 13, 2018 at 5:25 PM Robert Elz wrote: > [...] > > What's more, reporting bugs in bash 4.3 is just a waste of everyone's > time. > > Upgrade to (at least) the current released version, and use that instead. > > Adding to this point: > >

Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Eduardo Bustamante
On Mon, Aug 13, 2018 at 5:25 PM Robert Elz wrote: [...] > What's more, reporting bugs in bash 4.3 is just a waste of everyone's time. > Upgrade to (at least) the current released version, and use that instead. Adding to this point: * bash 4.3 was released 4 years ago (2014-02-26) * bash 4.4 is t

Re: Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Robert Elz
Date:Mon, 13 Aug 2018 11:51:08 -0400 From:Bize Ma Message-ID: | Bash since 4.3 fails to follow what the documentation describes as that on | an assignment values do not undergo splitting or globing. This is already fixed. What's more, reporting bugs in bash 4.

Assignment of $* to a var removes spaces on unset IFS.

2018-08-13 Thread Bize Ma
Executing this code: set -- " foo "" bar baz " " quux " unset IFS a=$* b="$*" printf '[%s]' "$a" "$b"; echo Leads to this results in several shells: ash : [ foo bar baz quux ][ foo bar baz quux ] dash: [ foo bar baz

Re: Unexpected delay in using arguments.

2018-08-13 Thread Bize Ma
Yes Greg, Please read the expanded source question, bash 5 with (and without) bash-malloc has been tested. https://unix.stackexchange.com/q/462084/265604 The problem with arguments is still present. 2018-08-13 9:37 GMT-04:00 Greg Wooledge : > On Sun, Aug 12, 2018 at 03:16:34AM -0400, Bize M

Re: Unexpected delay in using arguments.

2018-08-13 Thread Greg Wooledge
On Sun, Aug 12, 2018 at 03:16:34AM -0400, Bize Ma wrote: > Which is a thousand times slower. > Bash 5 is even worse Pre-release bash sources use a debugging-friendly (slow) malloc. Or something. Damn, google is not helping me out here.

Re: Extglob *?(a)b matches every string

2018-08-13 Thread Greg Wooledge
On Sat, Aug 11, 2018 at 09:26:56PM -0700, Mark Polyakov wrote: >Bash Version: 4.3 >Patch Level: 46 >A A A An extglob pattern such as `*?(anything)something_else` will >match any string, even though it should only match strings that end >with something_else. This appears to be

Re: Rational Range Interpretation for bash-5.0?

2018-08-13 Thread Bize Ma
On 08/06/2018 03:07 PM, Chet Ramey wrote: Hi. I am considering making bash glob expansion implement rational range interpretation starting with bash-5.0 -- basically making globasciiranges the default. It looks like glibc is going to do this for version 2.28 (at least for a-z, A-Z, and 0-9), and o