Re: Filename Expansion bug

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Filename Expansion bug
Date	2020-01-13 09:12 -0500
Message-ID	<mailman.2485.1578924767.1979.bug-bash@gnu.org> (permalink)
References	<CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com> <CAJV=ESGhY7Wu==vMeUS+icoLBYkONBxuUpTdoUsm3fv=EZFiEQ@mail.gmail.com> <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> <16319.1578706785@jinx.noi.kre.to> <72313627-e4fe-a4d8-3fbd-50b2847a9007@case.edu>

Show all headers | View raw

On 1/10/20 8:39 PM, Robert Elz wrote:

> That said, I also see no particularly good reason why bash should
> be the outlier here.

It's an artifact of the bash implementation.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: Filename Expansion bug Chet Ramey <chet.ramey@case.edu> - 2020-01-13 09:12 -0500

csiph-web