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

Path	csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From	Eduardo A. Bustamante López <dualbus@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Assignment of $* to a var removes spaces on unset IFS.
Date	Mon, 13 Aug 2018 20:17:52 -0700
Lines	46
Approved	bug-bash@gnu.org
Message-ID	<mailman.5083.1534216680.1292.bug-bash@gnu.org> (permalink)
References	<CAFra36g+5888jkADfSzEnP2ggKgN4XadFk91gHgnWUJ5BxNWWw@mail.gmail.com> <28958.1534206249@jinx.noi.kre.to> <CAOSMAutpQvzbwAgAv7QPc14tZ2PEi5tGPXWHfqrCY-k2AhVQSg@mail.gmail.com> <CAFra36gUtG8x8SoNP9fGNSp-X61EE0_yqebqHwqx9CXvhZ0S5w@mail.gmail.com> <20180814020952.GA20145@ubuntu> <CAFra36gomAjeH1qQpK8OFtJ1SgPbXrG+g6BV68PcEOb58v1Nvw@mail.gmail.com>
NNTP-Posting-Host	lists.gnu.org
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii
X-Trace	usenet.stanford.edu 1534216681 11302 208.118.235.17 (14 Aug 2018 03:18:01 GMT)
X-Complaints-To	action@cs.stanford.edu
Cc	Robert Elz <kre@munnari.oz.au>, bug-bash <bug-bash@gnu.org>, Chet Ramey <chet.ramey@case.edu>
To	Bize Ma <binaryzebra@gmail.com>
Envelope-to	bug-bash@gnu.org
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HX6wyU6DQ2TI/e/BPZwkp0yEKJA9rSRgOOIi3CN/sQA=; b=SJxBMVZVM0yJacP6yRCBlDhPU14BLqcTeZreOdom9RO0ujZIYuU+DZknl+vYc6zMnw UAmr2XaprYyVtAmA/oaQHQ1LUQBto4md9AhVig2DqULJqFjhRpXg1FkzZdQs9q6/sfvw b5Y+Pb7hBD3lF1KybQAUxYAVb334ZKUWtBuMqPkuMANS/opQi+IpOwqYuN0ppf3KkG+c bH7OHC66XyuugULgj8UenD/Pph3wb+G4kxPC83aTHWbDIyNGbpaeFPvB0dyPjkhtcJSp OD4hQpktdr29QDgcnW421QGLzTvwKJWBtifRIkXp7lbUCMMBtSba9nXjeU4IGlFTOP9Q dVFg==
X-Google-DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=HX6wyU6DQ2TI/e/BPZwkp0yEKJA9rSRgOOIi3CN/sQA=; b=p1QhmnUuMWcM3k9mFpijGMDyrOVZr0WoviMq+ST+64yl4iK+i0Q2hM0Zb0HEXEQfGz J+hyEq/Xoq+Sku66OdxCtZ4jnHPr9lOYoOLrfaZa/O18O8Ag7lZk9gqNbLsCFCORTDzS TJ6ImornSYiBimLYJhGci6gA0Ivm4l1nxFqUMmQtbS/CTCVkpO4AQHqjbzglHD3moNac rl/vYx73P/Qgc9s9xaIQQDDr0de21rEMrvy9C+I+1lAa5TWCZuKTMZ+is2QrshQ9dF5R zj2jTPIfT1kEON+YD+8W/qgNdRqZzyTgaDTE61WS9CDS6p0ZFX232VzVyM4Jsg95w+/e TXdQ==
X-Gm-Message-State	AOUpUlGJXsvwNLq2nJHTFyndHI2MHg6Z+xwKf5Th2o8uGzZq7apm6NKB CaWBH4BRtO0mSrqcUrUfxK0=
X-Google-Smtp-Source	AA+uWPyB9+slYSi7ebbDKR+uv/rYJE+7ul/BbGjJ/4wtmpyKCH+DsGpnVTl+EvzlCyWM6uXPxLmz/g==
X-Received	by 2002:a62:571b:: with SMTP id l27-v6mr21511606pfb.29.1534216674337; Mon, 13 Aug 2018 20:17:54 -0700 (PDT)
Mail-Followup-To	Bize Ma <binaryzebra@gmail.com>, Robert Elz <kre@munnari.oz.au>, bug-bash <bug-bash@gnu.org>, Chet Ramey <chet.ramey@case.edu>
Content-Disposition	inline
In-Reply-To	<CAFra36gomAjeH1qQpK8OFtJ1SgPbXrG+g6BV68PcEOb58v1Nvw@mail.gmail.com>
User-Agent	Mutt/1.10.1 (2018-07-13)
X-detected-operating-system	by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From	2607:f8b0:4864:20::42a
X-BeenThere	bug-bash@gnu.org
X-Mailman-Version	2.1.21
Precedence	list
List-Id	Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe	<https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive	<http://lists.gnu.org/archive/html/bug-bash/>
List-Post	<mailto:bug-bash@gnu.org>
List-Help	<mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe	<https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref	csiph.com gnu.bash.bug:14480

Show key headers only | View raw

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
important that you always test against the *unreleased* version of the code,
since that's where most bug fixes are queued up (or at least the ones that break
backwards compatibility).

> So? It is not solved in that thread, it is even said that:
> 
>  > 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.
> 

For some reason the threading broke in the archive browser. Here's the response
from Chet:

http://lists.nongnu.org/archive/html/bug-bash/2017-10/msg00023.html

The fix for this issue is already in the Git repository (devel branch) and in
Bash 5.0. 

I cannot answer for Chet, but please consider this:

The fix for this bug breaks backwards compatibility, so that means it cannot be
a patch-level fix for 4.4. It should either be a minor version increase (4.5) or
go into the next major release, which is 5.0 (which was already declared alpha
state, and includes the fix).

> It seems about time to get it solved. Or say that it won't be.

Again, it's fixed already and the fix is scheduled to go out in the next
release (5.0).

Given that, do you think this bug is severe enough to have to issue a new minor
version just for it? (4.5),

or can we just wait for 5.0 to come out which fixes this and a bunch of other
bugs? (see the CHANGES file, in particular, entry `oo',
http://git.savannah.gnu.org/cgit/bash.git/diff/CHANGES?h=bash-5.0-testing&id=9a51695bed07d37086c352372ac69d0a30039a6b)

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Assignment of $* to a var removes spaces on unset IFS. Eduardo A. Bustamante López <dualbus@gmail.com> - 2018-08-13 20:17 -0700

csiph-web