bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Command saved incorrectly in history.


From: Robert Elz
Subject: Re: Command saved incorrectly in history.
Date: Wed, 02 Sep 2026 06:49:03 +0700

    Date:        Tue, 1 Sep 2026 10:03:34 -0400
    From:        Chet Ramey <chet.ramey@case.edu>
    Message-ID:  <df37ac80-64c2-443f-b44f-4983dcc4f25f@case.edu>

  | https://austingroupbugs.net/view.php?id=267
  | "The format for a false pipeline is:

While that was originally in what was proposed, none of it seems to have
ever made into Issue 8 (the 2024 standard), despite it having been claimed
to have been applied in 2022.   Why it all vanished again I have no idea,
so while it explains why bash is as it is, none of it is relevant for
anything more than that.

I also cannot see any utility at all in (yet another way) to specify false.
I can see why some would want to be able to time more than simple commands
so (while I have no burning desire to need to implement it) I can see the
point of the time reserved word, but not the bare ! - that's just a pointless 
frill.

kre



reply via email to

[Prev in Thread] Current Thread [Next in Thread]