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

Groups > gnu.bash.bug > #15797 > 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 Andreas Schwab <schwab@suse.de> - 2020-01-09 13:01 +0100

#15797 — Re: Filename Expansion bug

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

[toc] | [standalone]

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

csiph-web