In bashref.html and probably some other files in doc/, pathname
expansion is referred to as filename expansion (see
https://www.gnu.org/software/bash/manual/bash.html#Filename-Expansion).
In bash.1, it is pathame expansion. Perhaps one of them should be
corrected.
--
konsolebox
On 8/20/19 3:38 AM, konsolebox wrote:
> In bashref.html and probably some other files in doc/, pathname
> expansion is referred to as filename expansion (see
> https://www.gnu.org/software/bash/manual/bash.html#Filename-Expansion).
> In bash.1, it is pathame expansion. Perhaps one of them should b
2019-08-20 10:08:10 -0400, Chet Ramey:
[...]
> However, at some point -- I can't find it now -- the GNU documentation
> standards recommended using "filename" and "filename expansion," reserving
> "pathname" for colon-separated values like $PATH.
[...]
I think you're refering to:
https://www.gnu.
2019-08-20 16:15:42 +0100, Stephane Chazelas:
[...]
> 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 sear
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
> GN
2019-08-20 16:30:21 +0100, Stephane Chazelas:
[...]
> See also "filename generation" or "globbing" which avoid the
> potential confusion with ~user and <(...) which also are
> "pathname expansion" operators.
[...]
FWIW, in zsh's manual, "filename expansion" refers to ~user, ~1,
~-1, ~named-directo
