Hello Bob
Thank you for your reply
On 15/09/17 02:57, Bob Proulx wrote:
Jonny Grant wrote:
Please keep my email address in any replies
Bob Proulx wrote:
Jonny Grant wrote:
Yes, it's a known limitation of POSIX that it uses a shared error code for
both files and directors, ENOENT.
On 17/09/17 06:25, Robert Elz wrote:
Date:Mon, 11 Sep 2017 22:49:47 +0300
From:Jonny Grant
Message-ID:
| How can an easy update to clarify message "No such file or directory"
| introduce a bug?
That's easy ... because it is not just t
On 11/09/17 20:58, Bob Proulx wrote:
Jonny Grant wrote:
Greg Wooledge wrote:
The wording is taken directly from perror() and related library calls,
as translated for your locale.
Yes, it's a known limitation of POSIX that it uses a shared error code for
both files and directors, E
On 29/08/17 16:35, Chet Ramey wrote:
On 8/29/17 8:40 AM, Jonny Grant wrote:
Hello
Could bash have some better handling of ENOENT for directories that don't
exist and files that don't exist?
Better than the error message the OS associates with that errno? The one
that comes str
Hello Greg!
On 29/08/17 16:21, Greg Wooledge wrote:
On Tue, Aug 29, 2017 at 03:40:54PM +0300, Jonny Grant wrote:
(B) is good, but (A) and (C) are problematic below.
A)
$ cd missingdir
bash: cd: missingdir: No such file or directory
How is this a problem? It seems completely clear to me
Hello
Could bash have some better handling of ENOENT for directories that
don't exist and files that don't exist?
(B) is good, but (A) and (C) are problematic below.
$ bash --version
GNU bash, version 4.3.48(1)-release (x86_64-pc-linux-gnu)
A)
$ cd missingdir
bash: cd: missingdir: No such f
