From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25133 invoked by alias); 4 Feb 2014 07:49:07 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 18386 Received: (qmail 27786 invoked from network); 4 Feb 2014 07:48:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <140203234859.ZM20535@torch.brasslantern.com> Date: Mon, 03 Feb 2014 23:48:59 -0800 In-reply-to: Comments: In reply to Francisco Borges "extended history time duration is broken? What does it measure?" (Feb 3, 10:43am) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: extended history time duration is broken? What does it measure? MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 3, 10:43am, Francisco Borges wrote: } Subject: extended history time duration is broken? What does it measure? } } I am running 4.3.17 and have EXTENDED_HISTORY set. The time duration for } each and every command in my shell history is always zero. I issue some } compilation commands that take nearly 20 minutes to run. } } What is the durantion time of EXTENDED_HISTORY supposed to measure exactly? Duration is not recorded when both INC_APPEND_HISTORY and SHARE_HISTORY are set, because the command is written out when it starts so it can be seen by other shells (rather than after it finishes) -- hence elapsed time is not known. I thought this was mentioned in either the docs or the FAQ, but I can't find the reference just now.