On 9/1/23 1:28 PM, Kerin Millar wrote:
On Fri, 1 Sep 2023 12:52:14 -0400
Dima Korobskiy <dkro...@gmail.com> wrote:
Kerin,
thanks for the workaround.
Just to clarify, is the issue specific to the `time` command?
I think that you would have to get an answer from Chet because yacc/bison
grammar is a little over my head. To that end, I have taken the liberty of
copying the bug-bash list back into this discussion.
That being said, it appears so. After reading your report, I tried to break the
parser in other, similar, ways but was not able to do so. I suppose that the
time keyword is special in so far as it expects to be given a pipeline.
It is the `time' keyword, and it is special, but not because it precedes a
pipeline. There are a bunch of special cases that have to be handled as the
result of https://www.austingroupbugs.net/view.php?id=267.
Note the twelve-year stretch between the initial issue submission, the
initial interpretation, and the final accepted text. Bash implements the
original interpretation from 2010.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
