From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10320 invoked from network); 27 Nov 2006 17:22:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 27 Nov 2006 17:22:51 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 49400 invoked from network); 27 Nov 2006 17:22:45 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 27 Nov 2006 17:22:45 -0000 Received: (qmail 19577 invoked by alias); 27 Nov 2006 17:22:34 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11043 Received: (qmail 19568 invoked from network); 27 Nov 2006 17:22:34 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 27 Nov 2006 17:22:34 -0000 Received: (qmail 47929 invoked from network); 27 Nov 2006 17:22:34 -0000 Received: from vms040pub.verizon.net (206.46.252.40) by a.mx.sunsite.dk with SMTP; 27 Nov 2006 17:22:29 -0000 Received: from torch.brasslantern.com ([71.116.86.88]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0J9E00CC0G6AIQ80@vms040.mailsrvcs.net> for zsh-users@sunsite.dk; Mon, 27 Nov 2006 11:20:35 -0600 (CST) Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id kARHKY73026898 for ; Mon, 27 Nov 2006 09:20:34 -0800 Received: (from schaefer@localhost) by torch.brasslantern.com (8.13.1/8.13.1/Submit) id kARHKYON026897 for zsh-users@sunsite.dk; Mon, 27 Nov 2006 09:20:34 -0800 Date: Mon, 27 Nov 2006 09:20:34 -0800 From: Bart Schaefer Subject: Re: What was the reason for history -D not reporting runtimes? In-reply-to: To: zsh-users@sunsite.dk Message-id: <061127092034.ZM26896@torch.brasslantern.com> MIME-version: 1.0 X-Mailer: OpenZMail Classic (0.9.2 24April2005) Content-type: text/plain; charset=us-ascii References: <17393e3e0611250841v6a5e3d73ha185b3f3b44509b9@mail.gmail.com> <20061127143109.GA26291@blorf.net> Comments: In reply to "Nikolai Weibull" "Re: What was the reason for history -D not reporting runtimes?" (Nov 27, 8:47am) On Nov 27, 8:47am, Nikolai Weibull wrote: } } Oh boy. Turns out extendedhistory wasn't on by default like I } thought. Anyway, even with it set it doesn't work. Can appendhistory } mess it up? } } Also, why isn't histsavebycopy set by default, as the documentation } suggests that it be set unless you have special needs? Neither of these is set by default because historically (no pun) zsh and other shells could [theoretically] all use the same history file. The two options you mention would break backwards compatibility if they were set. In almost every case of "why doesn't zsh do this fancy thing by default?" the answer is "because people have been using zsh since about 1990 and we don't want to unexpectedly break anyone's configuration on upgrade." Yeah, I know, nowadays other software routinely breaks everything about a past installation when you upgrade it, or at least requires you to go through some kind of automated conversion process from which there is no safe return short of restoring from a backup. That doesn't mean I like it when it happens.