Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #13756 > unrolled thread
| Started by | Clark Wang <dearvoid@gmail.com> |
|---|---|
| First post | 2018-02-27 10:18 +0800 |
| Last post | 2018-02-27 10:18 +0800 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Unset array doesn't work Clark Wang <dearvoid@gmail.com> - 2018-02-27 10:18 +0800
| From | Clark Wang <dearvoid@gmail.com> |
|---|---|
| Date | 2018-02-27 10:18 +0800 |
| Subject | Re: Unset array doesn't work |
| Message-ID | <mailman.9789.1519697949.27995.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web