Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: What was the reason for history -D not reporting runtimes?

X-seq: zsh-users 11040
From: Wayne Davison <wayned@xxxxxxxxxxxxxxxxxxxxx>
To: Nikolai Weibull <now@xxxxxxxx>
Subject: Re: What was the reason for history -D not reporting runtimes?
Date: Mon, 27 Nov 2006 06:31:09 -0800
Cc: zsh-users@xxxxxxxxxx
In-reply-to: <dbfc82860611250952w68b615ebl250e3d8ede444739@xxxxxxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
References: <dbfc82860611240516w403e14fes7ef5a8d29148512c@xxxxxxxxxxxxxx> <17393e3e0611250841v6a5e3d73ha185b3f3b44509b9@xxxxxxxxxxxxxx> <dbfc82860611250952w68b615ebl250e3d8ede444739@xxxxxxxxxxxxxx>

On Sat, Nov 25, 2006 at 06:52:50PM +0100, Nikolai Weibull wrote:
> Yes, but that I already have.  The -D information somehow isn't
> recorded.  I thought it was incappendhistory that caused this, but I
> don't have that set.

The SHARE_HISTORY option also causes this.  This is because the current
algorithm for sharing history writes out the history lines as soon as
you enter the command.  Perhaps we should revisit the reasons for this
design choice to see if we still agree that this is the best spot to do
the shared/inc-append history updating.

..wayne..

Follow-Ups:
- Re: What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull

References:
- What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull
- Re: What was the reason for history -D not reporting runtimes?
  - From: Nikolai Weibull

Messages sorted by: Reverse Date, Date, Thread, Author