+ bug-bash@ - all
>If you don't know where your files are, then what are you >doing, really? Really: I was testing for compatibility with multiple build systems. The problem is not that I don't know where some file is, the problem is that my script runs at different depths. Absolute paths don't work because project checkout location is unknown, relative paths don't work because of different depths, and an environment variable has all disadvantages of global variables plus the disadvantage of a hidden parameter. So the solution is to search the ancestor tree, and, well, it's a good feature. >Same-name files but in different dirs can have different contents and serve >different purposes. Exactly. And I wrote that is such cases one must use the directory name to disambiguate: `.../red-project/readme.txt` vs `.../green-project/readme.txt` ---------------- I apologize for a possible duplicate, looks like the modern mail clients have not been tested for interoperability with usenet mailing lists. ---------------- To: Bug Bash ([email protected]); Subject: Three Dots: Feature Request/Philosophical Bug Report; 05.10.2025, 11:17, "Pourko via Bug reports for the GNU Bourne Again SHell" <[email protected]>: On Sun, 05 Oct 2025 10:31:19 +0300, Michael Gasanenko wrote: *Proposal:* Let .../ (three dots) replace any number of ../ (parent directory) symbols, provided that the file name that follows [...] [...] the one that is found first. Same-name files but in different dirs can have different contents and serve different purposes. If you don't know where your files are, then what are you doing, really? Might as well request a feature that picks up a random file from anywhere on your disk -- just as well.
