From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28478 invoked by alias); 14 Feb 2015 21:47: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: 34546 Received: (qmail 19715 invoked from network); 14 Feb 2015 21:47:16 -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 X-Originating-IP: [86.6.153.127] X-Spam: 0 X-Authority: v=2.1 cv=VLdTnr/X c=1 sm=1 tr=0 a=39NrsSuza2clQiZR/7fYWQ==:117 a=39NrsSuza2clQiZR/7fYWQ==:17 a=kj9zAlcOel0A:10 a=NLZqzBF-AAAA:8 a=K4Me0lB2AAAA:8 a=LimtLNzH3U4cDMC2JVoA:9 a=CjuIK1q_8ugA:10 Date: Sat, 14 Feb 2015 21:37:57 +0000 From: Peter Stephenson To: Derek Gleim Cc: zsh workers Subject: Re: prexec never gets empty string? Message-ID: <20150214213757.010b0c82@ntlworld.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 13 Feb 2015 16:41:24 -0600 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? Sorry, no. I was misunderstanding completely --- I thought your error was that spaces were wrong in the line that was being output. As Mikael says, it's certainly not the case that preexec is supposed to veto lines based on the history. It's purpose is unrelated to the recording of history: it's there to pass information about the line about to be executed. pws