Re: Pathname expansion vs. filename expansion

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Pathname expansion vs. filename expansion
Date	2019-08-20 11:39 -0400
Message-ID	<mailman.511.1566315550.30381.bug-bash@gnu.org> (permalink)
References	<CAJnmqwY42QvC5FO_35efmPnuookSfvGm2_hWtxmaCp_FCSyhDw@mail.gmail.com> <87094e8a-3a60-5ad1-ac26-815a4a8a7ed7@case.edu> <20190820151542.6pvfuk32niplx7pt@chaz.gmail.com> <08e3c6ec-db76-f4fa-32ba-8d889dba1b98@case.edu>

Show all headers | View raw

On 8/20/19 11:15 AM, Stephane Chazelas wrote:

> I think you're refering to:
> 
> https://www.gnu.org/prep/standards/html_node/GNU-Manuals.html#GNU-Manuals
> 
> GNU> Please do not use the term “pathname” that is used in Unix
> GNU> documentation; use “file name” (two words) instead. We use the
> GNU> term “path” only for search paths, which are lists of directory
> GNU> names. 
> 
> So I guess that should be "file name expansion"

Yeah, that's a bridge too far. I could live with "filename generation."

-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Pathname expansion vs. filename expansion Chet Ramey <chet.ramey@case.edu> - 2019-08-20 11:39 -0400

csiph-web