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:11 -0500
Message-ID	<mailman.2484.1578924719.1979.bug-bash@gnu.org> (permalink)
References	<CAJV=ESGhY7Wu==vMeUS+icoLBYkONBxuUpTdoUsm3fv=EZFiEQ@mail.gmail.com> <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> <CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com> <8c2d195b-679c-08ca-cd01-2f4699995968@case.edu>

Show all headers | View raw

On 1/9/20 6:09 AM, Mickael KENIKSSI wrote:
> Thanks for your comment.
> 
> I understand this may not sound of primary importance for you since they 
> are canonically equivalent, but sometimes what we really all care about is 
> the path as a literal string (be it well- or ill-formed), and not the 
> filesystem object it points to.

Pathname expansion deals with that filesystem object, and those filesystem
objects have a single slash as the directory separator. That's how the
bash implementation deals with it.

> I suppose it all comes down to an implementation question.

Indeed, it does.

-- 
``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:11 -0500

csiph-web