fect reports applied.
>
> I hope this helps.
> regards
> Andrew
>
> > On 13 Jan 2022, at 13:02, Mark Galeck via austin-group-l at The Open Group
> > wrote:
> >
> > Yes thank you, this is very helpful.
> >
> > Right now, I point the customers to
Group wrote:
>
> Mark Galeck wrote, on 13 Jan 2022:
> >
> > Thank you Nick. So here's the one I just found.
> >
> > In the section 2.2.3 Double-Quotes, it says about \ :
> >
> > "The shall retain its special meaning as an escape
> > c
austingroupbugs.net ... if it is (a), then the
> maintainers of those shells are generally on this list too, and will take the
> appropriate action.
> --
> Nick
>
> On Wed, Jan 12, 2022 at 7:01 AM Mark Galeck via austin-group-l at The Open
> Group wrote:
>>
&
Hello,
a few years ago, I used to report a number of "bugs" on
www.austingroupbugs.net , however, my reporting was not acted upon,
which may be because I did not properly understand what you care about
or not.
So before I do that again, since I don't want to waste anybody's time,
I want to ask
>There is no precise definition of "acceptable"
Yes currently there isn't , but it would be easy to make such a definition,
simply, for various failure errno numbers (which are enumerated in the
standard), say "acceptable", "not acceptable", or perhaps "unspecified".
Yes, thank you, alternative 3, I was wrong.
Hello,
the shell standard section on Command Search and Execution, says
command shall be searched for using the PATH environment variable as described
in XBD Environment Variables
and that section says the value of PATH is split into a list and
"The list shall be searched from beginning to
Hello,
the current shell standard says in Section 2.9.1:
---
If no command name results, variable assignments shall affect the current
execution environment.
If the command name is not a special built-in utility or function, the variable
assignments (...) shall not affect the
Hello humans,
I had another question about the Shell Standard, but since nobody answered last
two, I reckon that the proper thing to do is to log them into "defect tracker".
I had previously been reluctant to do so, because if I am not sure something
was a defect, why should I log it as such.
Hello,
In the Shell Standard (current version 2016), section on Token Recognition, it
says
(...) shell shall break its input into tokens by applying the first applicable
rule below to the next character in its input.
and
The token shall be from the current position in the input (...)
Robert Elz graciously pointed out that 2.9.4 implictly says that ( is in fact
an operator, which solves my problem. Thank you to Robert!
- Original Message -
From: Mark Galeck <mark_gal...@pacbell.net>
To: "austin-group-l@opengroup.org" <austin-group-l@opengrou
Hello,
I thought the dash shell is strictly conforming to the POSIX shell standard.
But it seems, I see a discrepancy. It probably means, I don't understand the
standard. Please explain what is going on.
The standard says in the section 2.2.3 on Double-Quotes and $ : "even number of
Hello,
the formal POSIX shell grammar for yacc symbol "simple_command" accepts
commands which can be loosely summarized as:
three parts, each optional, in order:
variable assignments and redirections mixed togethercommand namecommand
arguments and redirections mixed together
It seems to me,
13 matches
Mail list logo
