Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail From: Ilkka Virta Newsgroups: gnu.bash.bug Subject: Re: Rational Range Interpretation for bash-5.0? Date: Wed, 15 Aug 2018 16:29:31 +0300 Lines: 20 Approved: bug-bash@gnu.org Message-ID: References: <1f2b7e3e-3dee-f5bb-7f0b-59393ae99902@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1534339782 10707 208.118.235.17 (15 Aug 2018 13:29:42 GMT) X-Complaints-To: action@cs.stanford.edu To: chet.ramey@case.edu, bug-bash Envelope-to: Bug-bash@gnu.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 In-Reply-To: <1f2b7e3e-3dee-f5bb-7f0b-59393ae99902@case.edu> Content-Language: en-US X-SASI-RCODE: 200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; h=subject:to:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=smtp; bh=+U9A64Llwf80K7jkbZRtmjdbWDNgvGyLxC+R5FrHZrs=; b=tN3vUW5f8VkduEvUDwhgstv965ePp0NtiEpe4LPBMPudQ5zEDq8kSJcyDh/4WxXLCFNjUl2gAHi+JqKlQPm0xPOpgNvJjGfJoWxomUCdoMVZmKpuSevoFb6cJmZb+YUIOk91TV7mVimKuH+QzY24IhYiYOTmzXoGgPxfy6Ha5kee429+DAHLVOe1/D+1yClXVcOX9wJSU0FqsLN4Mt+Poi1vlYRZT+F3Jw2bc1Ayqg+FZ1PcziGqGt2MUj8EH/sDW2jzfMsTcGp0tTcPADkypnvPRqldoNYaocyQPXpAlo/d8/dgq+CPC17RL79TCFs84O+ui6wmCFs1rpT+xvRczw== X-detected-operating-system: by eggs.gnu.org: FreeBSD 8.x X-Received-From: 157.24.2.213 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:14495 On 6.8. 23:07, Chet Ramey wrote: > Hi. I am considering making bash glob expansion implement rational range > interpretation starting with bash-5.0 -- basically making globasciiranges > the default. It looks like glibc is going to do this for version 2.28 (at > least for a-z, A-Z, and 0-9), and other GNU utilities have done it for some > time. What do folks think? I tried to think about a counterpoint, some case for where the current (non-globasciiranges) behaviour would be useful, but I can't come up with any. At least the part where [a-z] matches A, but not Z makes it a bit useless. If you're considering special-casing just those three, I'd suggest adding a-f and A-F too, for patterns matching hex digits. So yeah, +1 from me. -- Ilkka Virta / itvirta@iki.fi