Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15800 > unrolled thread

Re: Filename Expansion bug

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#15800 — Re: Filename Expansion bug

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/

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web