Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14482

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

Path csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From Pierre Gaston <pierre.gaston@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Assignment of $* to a var removes spaces on unset IFS.
Date Tue, 14 Aug 2018 10:49:05 +0300
Lines 64
Approved bug-bash@gnu.org
Message-ID <mailman.5086.1534232962.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> <20180814031752.GB20145@ubuntu>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1534232962 19387 208.118.235.17 (14 Aug 2018 07:49:22 GMT)
X-Complaints-To action@cs.stanford.edu
To "bug-bash@gnu.org" <bug-bash@gnu.org>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=YMxvesdV56oG4zIJrguRy8LTp0iAaqyO6zK+875LJk4=; b=NDiIbNEO1xMSYt3V3xcMN77I6sc19V0PO/yrR0XE+LFcrUEgGFQR7N0YlKA6pROQSl FUjTd7NnCIb1qXo9UWUKOoeES7c3wMiFk0P0M4X7uk0jH5hk3f9oginvRAaukZ0r5MQ6 N8j9Lz8AwXqIVxpz01xo7sqvYo81H5EDjDx0hjAgN8hxk0g30hInGGeIKmbwXgmivLKm GDCbp1eIw92x34p1UN7OdnAQBrVNWLwErIziI9vcTKO7PWpihG9WFAjjhXby3XM5tp3h 9biC4JBeZ2p5NJjoYh2U78vAcrQN7lc4eFqgDC+ExkseNhWn8jNPKa0/zlOCOL1bkkT/ 3vdw==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=YMxvesdV56oG4zIJrguRy8LTp0iAaqyO6zK+875LJk4=; b=U+rt72YJQTdNHnQ8F3OoPPPtMtow2TvAcCZ2JRyENAt3yyKaDvstTiRdcMtQtdg5Vr zoBGaJdZje8muf8L+ATFkI+A8Irj8MtwtpUuWE57oT4oOLqnOhzJiySfP+VpeIpxwyIp 6fgZE40Tfsa3fhNeEXwz1FI1wW6kwjRg0xlgfuvqtP6sV4kuVkN5t483mnjfvbS+HOoC 8UHLOrFu7AwAMQQf4NIu45HPgjBiPowNhxUN7TVisIl4Iy6vF9G1TS2fCA0nPOjkx4GX W/JUOEvl8hWYCZB7bF2GlEzw3BKPx5HAT9Gx/VALGfJl7iJqgsdtmXd9Jh1/xFZRn8rK WHyg==
X-Gm-Message-State AOUpUlE/Qv1xr7mhEv1kJiN496uyO/bZMb22e1SjT/BwZIW3mHEtxQFO RVOp/J6egs7SQDv0zsl6i7GfLVOm2tmI2fdMJL3kaA==
X-Google-Smtp-Source AA+uWPwd6nbgGp2Dqod5QSoxZdECVzMeoXXLPHNhWX+iB2qmO3qcJdSK58kaAyWGTp46113b6X69ujIAxcOB7oez0VA=
X-Received by 2002:a0c:d6c3:: with SMTP id l3-v6mr17934137qvi.154.1534232957591; Tue, 14 Aug 2018 00:49:17 -0700 (PDT)
In-Reply-To <20180814031752.GB20145@ubuntu>
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2607:f8b0:400d:c0d::233
X-Content-Filtered-By Mailman/MimeDel 2.1.21
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:14482

Show key headers only | View raw


On Tue, Aug 14, 2018 at 6:18 AM Eduardo A. Bustamante López <
dualbus@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 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. Pierre Gaston <pierre.gaston@gmail.com> - 2018-08-14 10:49 +0300

csiph-web