Re: unquoted expansion not working (was Re: Not missing, but very hard to see)

From	Robert Elz <kre@munnari.OZ.AU>
Newsgroups	gnu.bash.bug
Subject	Re: unquoted expansion not working (was Re: Not missing, but very hard to see)
Date	2019-12-15 06:12 +0700
Message-ID	<mailman.860.1576365213.1979.bug-bash@gnu.org> (permalink)
References	(8 earlier) <5DF2FE31.9070406@tlinx.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <17197.1576365173@jinx.noi.kre.to>

Show all headers | View raw

    Date:        Sat, 14 Dec 2019 02:48:16 -0800
    From:        L A Walsh <bash@tlinx.org>
    Message-ID:  <5DF4BDF0.6000402@tlinx.org>

  | it could break existing scripts that

Scripts should not be using brace expansion in the first place, it
is useful to save typing for interactive shells, but (whatever quoting
is or is not donw, and whatever ranges are supported)) it is just a lexical
expansion, which can easily be done in the script source, if you want to
assign that 'Z' .. 'a' range to an array, simply list the characters you
want (quoted as needed) and assign them.   That causes less problems long
term, and is more likely to be portable to more shells (even shells that
do brace expansion don't all do it in exactly the same way).

kre

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

Thread

Re: unquoted expansion not working (was Re: Not missing, but very hard to see) Robert Elz <kre@munnari.OZ.AU> - 2019-12-15 06:12 +0700

csiph-web