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 craf

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 > checkin

Fwd: Question

2017-09-05 Thread Saint Michael
Dear Maintainer Is there a commercial or free software that can take a Bash script and transparently turn it into a C executable, provided the machines where it runs has any of the external commands like awk, etc? Something like a Java virtual machine, for Shell. I think this language is powerful