From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-8269-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 20799 invoked from network); 5 Dec 2004 19:51:48 -0000
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by ns1.primenet.com.au with SMTP; 5 Dec 2004 19:51:48 -0000
Received: (qmail 18181 invoked from network); 5 Dec 2004 19:51:42 -0000
Received: from sunsite.dk (130.225.247.90)
  by a.mx.sunsite.dk with SMTP; 5 Dec 2004 19:51:42 -0000
Received: (qmail 8106 invoked by alias); 5 Dec 2004 19:50:52 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 8269
Received: (qmail 8092 invoked from network); 5 Dec 2004 19:50:52 -0000
Received: from unknown (HELO a.mx.sunsite.dk) (130.225.247.88)
  by sunsite.dk with SMTP; 5 Dec 2004 19:50:52 -0000
Received: (qmail 16756 invoked from network); 5 Dec 2004 19:49:53 -0000
Received: from dsl3-63-249-88-2.cruzio.com (HELO binome.blorf.net) (63.249.88.2)
  by a.mx.sunsite.dk with SMTP; 5 Dec 2004 19:49:51 -0000
Received: by binome.blorf.net (Postfix, from userid 1000)
	id 2D18341DA; Sun,  5 Dec 2004 11:49:52 -0800 (PST)
Date: Sun, 5 Dec 2004 11:49:51 -0800
From: Wayne Davison <wayned@users.sourceforge.net>
To: zsh-users@sunsite.dk
Subject: Re: history not saving elapsed times
Message-ID: <20041205194951.GA5469@blorf.net>
References: <20041204223007.GA9393@puritan.pcp.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041204223007.GA9393@puritan.pcp.ath.cx>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk
X-Spam-Level: 
X-Spam-Status: No, hits=-0.0 required=6.0 tests=BAYES_40 autolearn=no 
	version=2.63
X-Spam-Hits: -0.0

On Sat, Dec 04, 2004 at 11:30:07PM +0100, Nikolai Weibull wrote:
> Zsh isn't storing elapsed times in my history, all entries are like
> 	: <timestamp>:0;<cmd>

This happens if you use one of the incremental-append history options:
since zsh writes out the history line before running it, it doesn't know
what the elapsed time for the command will be, so it always writes it
out with an elapsed time of 0.

..wayne..