[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issues in bash found while creating command result display
From: |
Paul Wise |
Subject: |
Re: issues in bash found while creating command result display |
Date: |
Tue, 16 Apr 2019 10:29:36 +0800 |
User-agent: |
Evolution 3.30.5-1 |
On Mon, 2019-04-15 at 17:31 -0400, Chet Ramey wrote:
> You can use $HISTCMD with a slight fix that's now in the devel branch.
That doesn't increment when you use HISTCONTROL=erasedups AFAICT but
the command number does increment. Also HISTCMD doesn't start at zero.
> The Korn shell uses values > 256 to denote `internal' shell exit statuses,
> but that violates POSIX.
I wonder if bash could set an additional variable to indicate if $? is
from a normal exit, a signal exit, a shell keystroke etc, as well as a
corresponding equivalent array that is about PIPESTATUS.
> I'll keep that in mind for a future version.
Thanks for that.
--
bye,
pabs
https://bonedaddy.net/pabs3/
signature.asc
Description: This is a digitally signed message part
- issues in bash found while creating command result display, Paul Wise, 2019/04/14
- Re: issues in bash found while creating command result display, Chet Ramey, 2019/04/16
- Re: issues in bash found while creating command result display, Paul Wise, 2019/04/16
- Re: issues in bash found while creating command result display, Michael Felt (aixtools), 2019/04/17
- Re: issues in bash found while creating command result display, Chet Ramey, 2019/04/17