Re: Filename Expansion bug

From	Andreas Schwab <schwab@suse.de>
Newsgroups	gnu.bash.bug
Subject	Re: Filename Expansion bug
Date	2020-01-09 13:01 +0100
Message-ID	<mailman.2309.1578571298.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> <mvmpnfsx2ih.fsf@suse.de>

Show all headers | View raw

On Jan 09 2020, Mickael KENIKSSI wrote:

> 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.

But filename expansion is not operating on literal strings, it is
operating on existing filesystem objects.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

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

Thread

Re: Filename Expansion bug Andreas Schwab <schwab@suse.de> - 2020-01-09 13:01 +0100

csiph-web