Re: Backslash missing in brace expansion

From	Andreas Kusalananda Kähäri <andreas.kahari@abc.se>
Newsgroups	gnu.bash.bug
Subject	Re: Backslash missing in brace expansion
Date	2019-12-08 11:40 +0100
Message-ID	<mailman.518.1575801634.1979.bug-bash@gnu.org> (permalink)
References	(3 earlier) <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <20191208110003.bd50732fb2879caf0c1ebbe1@schrader-schulte.de> <20191208104016.GA79602@pooh.my.domain>

Show all headers | View raw

On Sun, Dec 08, 2019 at 11:00:03AM +0100, Martin Schulte wrote:
> Hello,
> 
> thanks a lot for all the answers!
> 
> I would like to suppose (Ilkka already argued in this direction) that in
> future versions of bash {x..C} should expand to x y z A B C.
> 
> Best regards,
> 
> Martin

Another idea would be to treat {x..C} just like {1..C} would be treated,
i.e as not a brace expansion at all but just as the literal string
{x..C}.

The current brace expansion impelementation in bash requires both points
of a range to be "of the same type".  This currently means "both must be
numbers, or both must be characters", but that second part could be made
stronger: "both must be characters with the same case".

It's obviously far too late to do anything about this at this point in
time.

-- 
Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden

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

Thread

Re: Backslash missing in brace expansion Andreas Kusalananda Kähäri <andreas.kahari@abc.se> - 2019-12-08 11:40 +0100

csiph-web