Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15576 > unrolled thread

Re: [FR] save command times and exit status in history automatically

Started byÁngel <angel@16bits.net>
First post2019-11-08 00:47 +0100
Last post2019-11-08 00:47 +0100
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [FR] save command times and exit status in history automatically Ángel <angel@16bits.net> - 2019-11-08 00:47 +0100

#15576 — Re: [FR] save command times and exit status in history automatically

FromÁngel <angel@16bits.net>
Date2019-11-08 00:47 +0100
SubjectRe: [FR] save command times and exit status in history automatically
Message-ID<mailman.871.1573170474.13325.bug-bash@gnu.org>
On 2019-11-07 at 12:18 -0800, Daniel Colascione wrote:
> Maybe what I
> really want is something like $?, but instead of containing exit
> status, it would contain information from a struct rusage (derived
> from wait4) for the last command. Or something like that anyway.

I would like having those variables, too. There was a related discussion
some time ago, and a workaround was mentioned (using PROMPT_COMMAND and
traps if I remember correctly), but I didn't like that approach too
much.

Would having such variables solve your needs? (using PROMPT_COMMAND to
copy them into a file, perhaps). I would expect that storing the values
from last wait4 would be much less intrusive than messing with history.


Kind regards

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web