Path: csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Bize Ma <binaryzebra@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Assignment of $* to a var removes spaces on unset IFS.
Date: Mon, 13 Aug 2018 21:36:23 -0400
Lines: 42
Approved: bug-bash@gnu.org
Message-ID: <mailman.5079.1534210589.1292.bug-bash@gnu.org>
References: <CAFra36g+5888jkADfSzEnP2ggKgN4XadFk91gHgnWUJ5BxNWWw@mail.gmail.com> <28958.1534206249@jinx.noi.kre.to> <CAOSMAutpQvzbwAgAv7QPc14tZ2PEi5tGPXWHfqrCY-k2AhVQSg@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Trace: usenet.stanford.edu 1534210590 7760 208.118.235.17 (14 Aug 2018 01:36:30 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: Eduardo Bustamante <dualbus@gmail.com>
Envelope-to: bug-bash@gnu.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=i6ivWH03zOnrhsfS3sno40Egxz6BspPeekMlqtzryYM=; b=jjBawz7YuFa2Rr3NPkO2c/AmEj0pPStZrcLuc5RlhWJ0o0ceB+E+2Rh9/VeNAxV0Kz x1ZcgsF/p6vB29GwJXvI9kHKgUTQq118S+7IFxrq2rXsB4UfVsT/oGduy89G16ZJWRhB wnmUMxUl6WfaFBLtwOPFID0vUKwhWcyYBVTCF35Mhct+2jg7HrAoIzYMWXdYt5klvxMv Ip1IBUv04MjydZ2yuHU4tgFrLfqIfTg8/tVqAEQI1YLrCqNV7+yKwQcx161b7Wup9CDU OGE0haqKulId3oim50WabbtzIVn/DjQYxyKo3MDZ8GI1P1+KxhZRdISamDMbh9IQ1HjC KNrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i6ivWH03zOnrhsfS3sno40Egxz6BspPeekMlqtzryYM=; b=Q2XESnVjo8mMBuwQgMIFyq2zv+q7dI2gteyiyOH+6Gt1bnelGqAmFn4jr5BfCPxVxO 1Stl+DUQiWzs8cwmi0l/Wo0XsPVPyDRTRlRr0Xk2Pdd5RD1TZT5MAlw4ifCVrGyzKXOz pJmObChG4G3YyCnzGHMKMmvm5lPkPYLVHr0cmDNfXl+ohkL75pOUfOXAeyax/hO7t+zk zvEcgZjI/QNoggiYJ+fx5cXLbs+pV32qocKDsJtAqnIwl+lg4ydunEf865dFdiNzxLzn uVk/fibNafhBq1RvNq2iXPySlD9pcrG0rhX9x8Ez1CP6ZVLM8q+3250DZFMvtbwozueT Jmvg==
X-Gm-Message-State: AOUpUlF6nxHdTzFHsS18jVJ8V9zGAlunn7VW5VsMeF63cKNsLOE2Swtb yjR35s805i2XDlRZMp8XU9tNmeF5RnqKvRrR52Q=
X-Google-Smtp-Source: AA+uWPyEIACCICaVhirVqeBOxLnEFQ78TTMlQDs4gOR39l3kfucy2eadv1IYkmr+tHEIVHBHlRFC6PViR9T/YePRN3M=
X-Received: by 2002:aca:3a03:: with SMTP id h3-v6mr19819282oia.270.1534210584246; Mon, 13 Aug 2018 18:36:24 -0700 (PDT)
In-Reply-To: <CAOSMAutpQvzbwAgAv7QPc14tZ2PEi5tGPXWHfqrCY-k2AhVQSg@mail.gmail.com>
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From: 2607:f8b0:4003:c06::22e
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:14477

2018-08-13 21:16 GMT-04:00 Eduardo Bustamante <dualbus@gmail.com>:

> On Mon, Aug 13, 2018 at 5:25 PM Robert Elz <kre@munnari.oz.au> 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 the current release of bash (2016-09-15)
> * bash 5.0 is in alpha state (2018-05-22)
>
>
You both are confused. The original table included

> b43sh           : [foo bar baz quux][  foo     bar  baz     quux  ]
> b44sh           : [foo bar baz quux][  foo     bar  baz     quux  ]

That's   4.3.48(2)-release   and    4.4.19(2)-release


Both are failing.

Note that 4.4.19 is newer than what is available in
https://www.gnu.org/software/bash/

The report is valid for present releases.
The bug is still present (since 4.3).

Please, do not waste our time in incorrect claims.

Do your homework and test !


> I know that some stable Linux distributions might still be
> distributing 4.3, but that just means that you have to report the bug
> against these distros, not upstream.


That is not the problem, don't jump to conclusions.