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 clearer
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 witho
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 that one message, yo
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 that one message, you change that
to "no directory" (or something
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() fl
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. Whi
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 handl
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 cli
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 craf
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
> checkin
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 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. It
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, t
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, wh
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
15 matches
Mail list logo
