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

2018-08-15 8:44 GMT-04:00 Greg Wooledge : > This reply was sent to me without Cc-ing the list. I have added the Cc. > > On Tue, Aug 14, 2018 at 11:39:20PM -0400, Bize Ma wrote: > > On Tue, 14 Aug 2018 12:34:31, Greg Wooledge said: > > > > > I will also repeat, once more, my advice that one

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

On 8/14/18 8:34 AM, Greg Wooledge wrote: > On Mon, Aug 13, 2018 at 09:36:23PM -0400, Bize Ma wrote: >> Note that 4.4.19 is newer than what is available in >> https://www.gnu.org/software/bash/ > > The current patch level of bash can be obtained by downloading the most > recent tarball from

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

On 8/13/18 10:52 PM, Bize Ma wrote: >  > This is a bug in bash and it should be fixed, not excused. > > To which I agree. After a year, nothing else have been said about it. > > It seems about time to get it solved. Or say that it won't be. It's fixed in the current development versions, and

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

On 15.8. 15:44, Greg Wooledge wrote: glob() { # "Return" (write to stdout, one per line) the expansions of all # arguments as globs against the current working directory. printf %s\\n $* } But... but... but... the PREVIOUS glob worked! Why didn't this one work? I'm sure you

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

This reply was sent to me without Cc-ing the list. I have added the Cc. On Tue, Aug 14, 2018 at 11:39:20PM -0400, Bize Ma wrote: > On Tue, 14 Aug 2018 12:34:31, Greg Wooledge said: > > > I will also repeat, once more, my advice that one should NEVER write > > a script containing an unquoted $*

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

2018-08-13 23:17 GMT-04:00 Eduardo A. Bustamante López : > On Mon, Aug 13, 2018 at 10:52:20PM -0400, Bize Ma wrote: > (...) My point is that, in the context of bug reports, it's > important that you always test against the *unreleased* version of the > code, > Not if the version to test is the

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

On Mon, Aug 13, 2018 at 09:36:23PM -0400, Bize Ma wrote: > Note that 4.4.19 is newer than what is available in > https://www.gnu.org/software/bash/ The current patch level of bash can be obtained by downloading the most recent tarball from and then applying the

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

On Tue, Aug 14, 2018 at 6:18 AM Eduardo A. Bustamante López < dual...@gmail.com> wrote: > 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

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

Date:Mon, 13 Aug 2018 21:36:23 -0400 From:Bize Ma Message-ID: | You both are confused. The original table included You misinterpreted my message. I said two independant things ... first that the bug is already fixed. I didn't say that the fixed version was

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

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

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

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 >

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

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

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

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.

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

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

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

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

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