Hi
My thoughts regarding which properties / fields can be useful to have in
history (originally pertaining to another shell but hope it's helpful):
https://github.com/ngs-lang/ngs/wiki/History-Design#commands-history
Regards,
Ilya
On 8 Nov 2019, at 1:47, Ángel mailto:an...@16bits.net>> wrote:
On 2019/11/07 12:18, Daniel Colascione wrote:
>>> 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 addition
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
> On 2019 Nov 7 , at 3:18 p, Daniel Colascione wrote:
>
> On Thu, Nov 7, 2019 at 12:09 PM Chet Ramey wrote:
>>
>> 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 li
On Thu, Nov 7, 2019 at 12:09 PM Chet Ramey wrote:
>
> 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.
Fair
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
Right now, bash history saves only the command line actually executed.
Why not also, optionally, save command execution times and exit
statuses? This information is practically free to collect.
