Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: unquoted expansion not working (was Re: Not missing, but very hard to see) Date: Mon, 16 Dec 2019 11:39:06 -0500 Lines: 24 Approved: bug-bash@gnu.org Message-ID: References: <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <5DF2987E.5000309@tlinx.org> <568aeaaa-22b3-c7b9-0e18-a92bef6d2ffb@iki.fi> <5DF2FE31.9070406@tlinx.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> <20191216163906.GV851@eeg.ccf.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: usenet.stanford.edu 1576514379 2934 209.51.188.17 (16 Dec 2019 16:39:39 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org Mail-Followup-To: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: <5DF4BDF0.6000402@tlinx.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: <20191216163906.GV851@eeg.ccf.org> X-Mailman-Original-References: <5b5064a8-7175-42e7-1eb5-6374dee6c11e@redhat.com> <21761e28-c496-ff67-d7b7-628c9325085f@iki.fi> <9dd3a388-39b1-c059-de99-813f1e411764@case.edu> <5DF2987E.5000309@tlinx.org> <568aeaaa-22b3-c7b9-0e18-a92bef6d2ffb@iki.fi> <5DF2FE31.9070406@tlinx.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> Xref: csiph.com gnu.bash.bug:15738 On Sat, Dec 14, 2019 at 02:48:16AM -0800, L A Walsh wrote: > On 2019/12/13 10:42, Greg Wooledge wrote: > > There's a larger issue to be addressed first. The man page says, > > [...] > > sary. When characters are supplied, the expression expands to each > > character lexicographically between x and y, inclusive, using the de‐ > > fault C locale. > ---- > If it says letters that lends stronger support to including > unicode ranges of letters and numbers since the shell handles unicode and > brace expansions with unicode filenames works just fine. That ranges don't > seems a bit of a wart. No, it won't include Unicode, because it very clearly says "C locale" right up there. The problem is, it is *not possible* to extract the set of characters out of an arbitrary locale. The locale interfaces simply are not built to allow it. You can do it in the C locale, simply because the C locale is a known, fixed quantity that you can hard-code. You can't do it in any other locale.