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
On 11/6/19 4:37 PM, Oğuz wrote:
cat <
Thanks for the report. Bash has, for some years, allowed EOF/EOS to
terminate a command substitution in certain circumstances, but this really
only shows up when you're expanding it inside a here-document. There is a
(relatively cryptic) warning message, b
