Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #13768 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2018-02-28 09:51 -0500 |
| Last post | 2018-02-28 09:51 -0500 |
| 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: Double substitution issue Greg Wooledge <wooledg@eeg.ccf.org> - 2018-02-28 09:51 -0500
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2018-02-28 09:51 -0500 |
| Subject | Re: Double substitution issue |
| Message-ID | <mailman.9861.1519829521.27995.bug-bash@gnu.org> |
On Wed, Feb 28, 2018 at 03:25:21AM -0500, William Entriken wrote:
> from=1
> to=3
> ls {$from..$to}
> Bash fails the chained substitution with:
>
> ls: {1..3}: No such file or directory
This is simply not a feature that bash implements. Bash does the
expansions in the opposite order (brace expansion first, then parameter
expansion second), so it does not work.
If you want to open a feature request for it, I'll let Chet respond.
Back to top | Article view | gnu.bash.bug
csiph-web