Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15329 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-08-20 11:39 -0400 |
| Last post | 2019-08-20 11:39 -0400 |
| Articles | 1 — 1 participant |
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.
Re: Pathname expansion vs. filename expansion Chet Ramey <chet.ramey@case.edu> - 2019-08-20 11:39 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-08-20 11:39 -0400 |
| Subject | Re: Pathname expansion vs. filename expansion |
| Message-ID | <mailman.511.1566315550.30381.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web