Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15734 > unrolled thread
| Started by | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| First post | 2019-12-15 06:12 +0700 |
| Last post | 2019-12-15 06:12 +0700 |
| 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: 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
| From | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| Date | 2019-12-15 06:12 +0700 |
| Subject | Re: unquoted expansion not working (was Re: Not missing, but very hard to see) |
| Message-ID | <mailman.860.1576365213.1979.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web