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
Dear Bob
I use Linux. My business to provide services for problems that I solve, as
you mention, by calling Awk, sed, join, etc., and databases. I allow my
customers to login to a box that I provide in my datacenter. I cannot
accept that it is impossible to restrict them to only call my *,sh script
Saint Michael wrote:
> Dear Maintainer
Note that I am not the 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?
Not as far as I am
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
Chet Ramey wrote:
> On 9/8/17 4:18 AM, Philipp Sasse wrote:
> > Executing something like
> > echo "foo
> > bar" | sed '/foo/!d'
> > results in an error. Apparently the history expansion considers only
> > quoting characters on the same input line, so the closing double quote is
> >
