Re: Unset array doesn't work

From	Clark Wang <dearvoid@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: Unset array doesn't work
Date	2018-02-27 10:18 +0800
Message-ID	<mailman.9789.1519697949.27995.bug-bash@gnu.org> (permalink)
References	(2 earlier) <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>

Show all headers | View raw

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?

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

Thread

Re: Unset array doesn't work Clark Wang <dearvoid@gmail.com> - 2018-02-27 10:18 +0800

csiph-web