On Wed, May 3, 2023, 16:25 Chet Ramey <chet.ra...@case.edu> wrote: > On 4/23/23 1:56 PM, Mark Schlegel wrote: > > Bash has a history function, it would be useful if 'history' would show > the exit codes (return codes) from all commands: > > Thanks for the proposal. There have been various suggestions over the years > about additional information attached to each history entry, including > $PWD, $?, etc., but there are issues with doing that. Where $? starts to > get messy, for example, is with asynchronous commands -- how do you tie the > exit status of an arbitrary background job back to the right history entry? >
by wait -n $pid alike -- > ``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/ > > >