Re: Filename Expansion bug

2020-01-13 Thread Chet Ramey

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, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/



Re: Filename Expansion bug

2020-01-13 Thread Chet Ramey

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, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/