From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13969 invoked by alias); 13 Feb 2015 23:14:17 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 34540 Received: (qmail 238 invoked from network); 13 Feb 2015 23:14:05 -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=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2y3cJ0u/I9gEFd4QRAvVq8NRguyKhPcymo22WaPQuXk=; b=Zz/NdzsDUV/WacLTkxQhsyQnKQP3R5b0vySR2ojyMGYXMwTSc7rz1H4hGsi697ZFJD Z9ynL/Wl+k5GVSZsXZ1bMg1tYzLvRgHzngEf/xxLcpJhT3T4cVdt2ECvWBLwAkeVN83/ uDQ/OTNEfFLuH1+E7k82YjJ6rg3fi3KsN5+uu5ipB1h5llIABroHBjfrfm9ql4wSDBQP 9V9KkVw+HvII1OGqioqqOp/Cc6X4SOUbOuy4/ULdDwuNHXpC2RmuieHVIN2gprTMxObY EkHPs980Dwluxj8GNPPjpAs2ceWqS8qQGOj13yITf1PHpRobQwgWThQCsu4Aqh+zB01J et2w== MIME-Version: 1.0 X-Received: by 10.42.112.199 with SMTP id z7mr17500152icp.46.1423869243624; Fri, 13 Feb 2015 15:14:03 -0800 (PST) In-Reply-To: References: Date: Sat, 14 Feb 2015 00:14:03 +0100 Message-ID: Subject: Re: prexec never gets empty string? From: Mikael Magnusson To: Derek Gleim Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On Sat, Feb 14, 2015 at 12:04 AM, Mikael Magnusson wrote: > On Fri, Feb 13, 2015 at 11:41 PM, Derek Gleim wrote: >>> I certainly would never want preexec to be disabled just because a >> line isn't stored in history. >> >> I don't follow. Me neither. My understanding is if the line isn't going to >> be stored, preexec is still called, but it is supposed to be given an empty >> string as the first argument when the command will be ignored by history >> (while the second and third arguments give you the command regardless). No? > > Judging by http://www.zsh.org/mla/workers/2001/msg00605.html , the > empty string was never intended as a feature, just a workaround for > not having access to the string. I guess a subsequent change made the > string always be available. Possibly the feature that always keeps the > last command in history until you run another command is newer than > this change and is why it always works now. Yep, here we are, the month after: http://www.zsh.org/mla/workers/2001/msg01028.html So this part of the manual was only accurate for about 21 days in 2001. -- Mikael Magnusson