From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11349 invoked by alias); 1 Jun 2011 06:24:54 -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: 29415 Received: (qmail 17414 invoked from network); 1 Jun 2011 06:24:51 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) 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.1 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110531232436.ZM11353@torch.brasslantern.com> Date: Tue, 31 May 2011 23:24:36 -0700 In-reply-to: <18618.1306874237@pws-pc.ntlworld.com> Comments: In reply to Peter Stephenson "PATCH: print -S uses lexical history" (May 31, 9:37pm) References: <18618.1306874237@pws-pc.ntlworld.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org (Zsh hackers list) Subject: Re: PATCH: print -S uses lexical history MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On May 31, 9:37pm, Peter Stephenson wrote: } } As we've had all the pain of the HIST_LEX_WORDS option, which almost no } one is using, to split a history line into words using the lexical } analyser, it's worth making this available directly using a relative of } "print -s" imaginatively called "print -S". This is nice, but I have to ask ... why not just make the behavior of "print -s" dependend on the current setting of the option? In what circumstances would one wish to (be able to choose at the level of individual commands to) have part of the history in lexed form and part of it not? I guess strictly speaking one already gets that effect when the option is off, as the loaded history will be unlexed and the interactively appeneded remainder lexed; so one could also argue that "print -s" should simply always go the lexing route, but I suppose there are also cases where speed might be a factor.