Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: [FR] save command times and exit status in history automatically
Date: Thu, 7 Nov 2019 15:09:00 -0500
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.847.1573157347.13325.bug-bash@gnu.org>
References: <CAKOZuevfhS7veH9+GSc=8StpgrA_vy59Y2fYYGhMDk0OPZb69Q@mail.gmail.com> <8e19b0fc-4183-90fa-b067-9da636998d6f@case.edu>
Reply-To: chet.ramey@case.edu
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: chet.ramey@case.edu
To: Daniel Colascione <dancol@google.com>, "bash.bug list" <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
In-Reply-To: <CAKOZuevfhS7veH9+GSc=8StpgrA_vy59Y2fYYGhMDk0OPZb69Q@mail.gmail.com>
Content-Language: en-US
Precedence: list
Xref: csiph.com gnu.bash.bug:15573

On 11/5/19 12:49 PM, Daniel Colascione wrote:
> Right now, bash history saves only the command line actually executed.

This isn't quite the case. What it saves is the line returned from 
readline, before it's expanded or executed.

> Why not also, optionally, save command execution times and exit
> statuses? This information is practically free to collect.

Because by the time you gather this information, the command has already
been saved completely.

There have been various proposals to extend the timestamp with additional
information, but it's all data you can gather when the timestamp is saved
before the command is executed.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/