Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: Filename Expansion bug
Date: Mon, 13 Jan 2020 09:11:51 -0500
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.2484.1578924719.1979.bug-bash@gnu.org>
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>
Reply-To: chet.ramey@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
Cc: chet.ramey@case.edu, bug-bash@gnu.org
To: Mickael KENIKSSI <k.mickael@gmail.com>
Envelope-to: bug-bash@gnu.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
In-Reply-To: <CAJV=ESHn1G2+9FSdtpTPT+CtqahNMiWJtRTE71PagS=H+2VA8A@mail.gmail.com>
Content-Language: en-US
Precedence: list
Xref: csiph.com gnu.bash.bug:15800

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/