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


Groups > gnu.bash.bug > #15709

Re: Backslash missing in brace expansion

Path csiph.com!3.us.feeder.erje.net!feeder.erje.net!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Andreas Kusalananda Kähäri <andreas.kahari@abc.se>
Newsgroups gnu.bash.bug
Subject Re: Backslash missing in brace expansion
Date Sun, 8 Dec 2019 11:40:16 +0100
Lines 29
Approved bug-bash@gnu.org
Message-ID <mailman.518.1575801634.1979.bug-bash@gnu.org> (permalink)
References <20191205201157.cd481936f76d95bbdfabc73c@schrader-schulte.de> <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <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>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=iso-8859-1
Content-Transfer-Encoding 8bit
X-Trace usenet.stanford.edu 1575801635 8861 209.51.188.17 (8 Dec 2019 10:40:35 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash@gnu.org
To Martin Schulte <gnu@schrader-schulte.de>
Envelope-to bug-bash@gnu.org
Mail-Followup-To Martin Schulte <gnu@schrader-schulte.de>, bug-bash@gnu.org
Content-Disposition inline
In-Reply-To <20191208110003.bd50732fb2879caf0c1ebbe1@schrader-schulte.de>
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 158.174.61.227
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <20191208104016.GA79602@pooh.my.domain>
X-Mailman-Original-References <20191205201157.cd481936f76d95bbdfabc73c@schrader-schulte.de> <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <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>
Xref csiph.com gnu.bash.bug:15709

Show key headers only | 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