Re: Bash handling of ENOENT on missing files and directories

2017-10-08 Thread PePa
On 10/09/2017 05:30 AM, Jonny Grant wrote: Fair enough. I agree it has been around for longer, but meant that POSIX standardized on that limitation, and didn't offer a better solution that clarified, eg ENOENTF ENOENTD I'm guessing not making the distinction saved a bit of CPU. yes, a

Re: Bash handling of ENOENT on missing files and directories

2017-10-08 Thread Jonny Grant
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. Which

Re: Bash handling of ENOENT on missing files and directories

2017-09-19 Thread Jonny Grant
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

Re: Bash handling of ENOENT on missing files and directories

2017-09-16 Thread Robert Elz
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

Re: Bash handling of ENOENT on missing files and directories

2017-09-14 Thread Bob Proulx
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. Which without programmers handling and > > > checking the stat()

Re: Bash handling of ENOENT on missing files and directories

2017-09-11 Thread Jonny Grant
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, ENOENT.

Re: Bash handling of ENOENT on missing files and directories

2017-09-11 Thread Bob Proulx
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, ENOENT. Which without programmers

Re: Bash handling of ENOENT on missing files and directories

2017-09-06 Thread Gerard Seibert
On Tue, 5 Sep 2017 10:57:20 -0400, Greg Wooledge stated: >Keep following this slippery slope and you get Microsoft Windows error >messages that say nothing useful at all. "An error has occurred." True, to a point. However, launching the "C:\WINDOWS\System32\eventvwr.exe" application and then

Re: Bash handling of ENOENT on missing files and directories

2017-09-05 Thread Chet Ramey
On 9/5/17 10:57 AM, Greg Wooledge wrote: > Keep following this slippery slope and you get Microsoft Windows error > messages that say nothing useful at all. "An error has occurred." I'd like to think we've evolved from ed's single all-purpose error message: `?'. -- ``The lyf so short, the

Re: Bash handling of ENOENT on missing files and directories

2017-09-05 Thread Greg Wooledge
On Tue, Sep 05, 2017 at 12:18:40AM +0300, Jonny Grant wrote: > > > $ cd missingdir > > > bash: cd: missingdir: No such file or directory > Yes, it's a known limitation of POSIX that it uses a shared error code for > both files and directors, ENOENT. Which without programmers handling and >

Re: Bash handling of ENOENT on missing files and directories

2017-09-04 Thread Jonny Grant
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 straight from

Re: Bash handling of ENOENT on missing files and directories

2017-08-29 Thread Chet Ramey
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 straight from strerror()? -- ``The lyf so short,

Re: Bash handling of ENOENT on missing files and directories

2017-08-29 Thread Greg Wooledge
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. It tells you what program generated the error,