Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Andreas Schwab Newsgroups: gnu.bash.bug Subject: Re: Filename Expansion bug Date: Thu, 09 Jan 2020 13:01:10 +0100 Lines: 17 Approved: bug-bash@gnu.org Message-ID: References: <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: usenet.stanford.edu 1578571299 7219 209.51.188.17 (9 Jan 2020 12:01:39 GMT) X-Complaints-To: action@cs.stanford.edu Cc: chet.ramey@case.edu, bug-bash@gnu.org To: Mickael KENIKSSI Envelope-to: bug-bash@gnu.org X-Virus-Scanned: by amavisd-new at test-mx.suse.de X-Yow: I love FRUIT PICKERS!! In-Reply-To: (Mickael KENIKSSI's message of "Thu, 9 Jan 2020 12:09:22 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] [fuzzy] X-Received-From: 195.135.220.15 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: <66b2510f-a2cf-b4d3-4574-9193a9bc89c4@case.edu> Xref: csiph.com gnu.bash.bug:15797 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."