I would assume that this is implied by "start-end".
I agree with you, and I think the documentation is fine. I was just
pointing out that specifying an invalid start/end element results in an
error and an exit status of 1, but specifying an invalid end-start range
results in silence and an ex
On 2/26/21 12:27 PM, Christopher Gurnee wrote:
Also somewhat related, deleting a range of history only works if it's
specified oldest to newest.
I would assume that this is implied by "start-end". Should the
documentation clarify that end < start is undefined behavior?
--
``The lyf so short, t
On Fri, Feb 26, 2021 at 12:41:44PM -0500, Chet Ramey wrote:
> On 2/26/21 11:22 AM, Mike Jonkmans wrote:
>
> > I don't think that f.i. precedence was taught.
> > Although you get that with arithmetic, which also has a grammar.
>
> It's not taught as such. Kids today are taught operator precedence,
On 2/26/21 11:22 AM, Mike Jonkmans wrote:
I don't think that f.i. precedence was taught.
Although you get that with arithmetic, which also has a grammar.
It's not taught as such. Kids today are taught operator precedence,
phrased as "order of operations": PEMDAS.
--
``The lyf so short, the cr
Also somewhat related, deleting a range of history only works if it's
specified oldest to newest. Deleting in the other direction is a noop
(no diagnostic either), e.g.:
history -d 20-10
does nothing if the range 10-20 exists, or prints an `out of range`
error otherwise. It probably makes
On 2/25/21 2:06 PM, Christopher Gurnee wrote:
Bash Version: 5.1
Patch Level: 4
Release Status: release
Git Commit: f3a35a2d (current master)
I don't really know the contribution rules for bash; my apologies in
advance if I'm missing anything or otherwise doing something wrong.
Description:
`
On Fri, Feb 26, 2021 at 02:54:07AM +0100, Ángel wrote:
> On 2021-02-26 at 00:45 +0100, Mike Jonkmans wrote:
> > On Thu, Feb 25, 2021 at 11:15:36PM +0100, Ángel wrote:
> >
> > Those grammars weren't all that different from yacc's grammar.
> > Just simpler and incomplete.
> >
> > Minimal example:
>
On Thu, Feb 25, 2021 at 06:28:34PM -0500, Chet Ramey wrote:
> On 2/25/21 10:13 AM, Mike Jonkmans wrote:
> > Starting with 'Statements' might be an option.
>
> Maybe. Or a POSIX-like description that says a command can be a
>
> simple command
> list
> pipeline
> compound command
> function defini
