Path: csiph.com!weretis.net!feeder6.news.weretis.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!171.64.64.130.MISMATCH!usenet.stanford.edu!not-for-mail
From: Clark Wang <dearvoid@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: Unset array doesn't work
Date: Tue, 27 Feb 2018 10:18:24 +0800
Lines: 16
Approved: bug-bash@gnu.org
Message-ID: <mailman.9789.1519697949.27995.bug-bash@gnu.org>
References: <790ade74-690f-541c-9ab4-6359917442d0@case.edu> <a56e05b1-0b34-1cb2-6073-91c12f27e228@gmail.com> <a642644f-e475-6361-140e-5b47ab4e321c@case.edu> <755d61fa-d2bc-8855-bc30-4388aff40691@gmail.com> <9974.1519637469@jinx.noi.kre.to> <F9DB73D6-F1EF-4F50-8302-3D42D72C1FB4@gmail.com> <20180226150717.el6qws5ubudnogaj@eeg.ccf.org>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: "bash.bug list" <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <20180226150717.el6qws5ubudnogaj@eeg.ccf.org>
Precedence: list
Xref: csiph.com gnu.bash.bug:13756

On Mon, Feb 26, 2018 at 11:07 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Mon, Feb 26, 2018 at 09:57:10AM -0500, Clint Hepner wrote:
> > If necessary, you can define a global (at the expense of a single
> subprocess)
> >
> >     myIFS=$(printf ' \t\n')
>
> That actually won't work, because $(...) strips the trailing newline(s).
> This might work:
>
> myIFS=$(printf ' \t\nx') myIFS=${myIFS%x}
>

What about myIFS=$(printf ' \n\t')? Does the order of chars in IFS make a
difference?