Re: Brace expansion ordering vs. parameter expansion

2021-04-29 Thread Chet Ramey
On 4/29/21 12:59 PM, Tom (AST) Watson wrote: All... I've resigned to having it the way it is, but I note that the solution doesn't need the backslash escape: [tsw@box6 ~]$ k=10 [tsw@box6 ~]$ eval echo {1..$k} 1 2 3 4 5 6 7 8 9 10 This one doesn't, but putting in the slash skips the first

RE: Re: Brace expansion ordering vs. parameter expansion

2021-04-29 Thread Tom (AST) Watson
themselves. Thanks for the input. It has been helpful. ...Tom -Original Message- From: Chet Ramey Sent: Thursday, April 29, 2021 07:46 To: Ilkka Virta Cc: chet.ra...@case.edu; Tom (AST) Watson ; bug-bash@gnu.org Subject: [External] Re: Brace expansion ordering vs. parameter expansion On

Re: Brace expansion ordering vs. parameter expansion

2021-04-29 Thread Chet Ramey
On 4/29/21 8:12 AM, Ilkka Virta wrote: Maybe, but it's never worked that way and was never intended to. You can get what you need using eval: eval echo \{1..${i}} BTW, was there some background to why they're ordered like this? I'm not sure if I have heard the story, and didn't

Re: Brace expansion ordering vs. parameter expansion

2021-04-29 Thread Greg Wooledge
On Thu, Apr 29, 2021 at 03:12:09PM +0300, Ilkka Virta wrote: > BTW, was there some background to why they're ordered like this? I'm not > sure if I have heard the story, and didn't see anything about it in Greg's > wiki or bash-hackers.org (of course they tell the "what", but not the > "why"). I

Brace expansion ordering vs. parameter expansion

2021-04-29 Thread Ilkka Virta
On Thu, Apr 29, 2021 at 4:18 AM Chet Ramey wrote: > Maybe, but it's never worked that way and was never intended to. You can > get what you need using eval: > > eval echo \{1..${i}} > BTW, was there some background to why they're ordered like this? I'm not sure if I have heard the story, and