Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15709 > unrolled thread

Re: Backslash missing in brace expansion

Started byAndreas Kusalananda Kähäri <andreas.kahari@abc.se>
First post2019-12-08 11:40 +0100
Last post2019-12-08 11:40 +0100
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.


Contents

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

#15709 — Re: Backslash missing in brace expansion

FromAndreas Kusalananda Kähäri <andreas.kahari@abc.se>
Date2019-12-08 11:40 +0100
SubjectRe: Backslash missing in brace expansion
Message-ID<mailman.518.1575801634.1979.bug-bash@gnu.org>
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

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web