From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8473 invoked by alias); 1 Mar 2014 02:31:00 -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: 32451 Received: (qmail 13818 invoked from network); 1 Mar 2014 02:30:53 -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: <140228183037.ZM5759@torch.brasslantern.com> Date: Fri, 28 Feb 2014 18:30:37 -0800 In-reply-to: <1190.1393633237@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "PATCH: make get-line widget update history number" (Mar 1, 1:20am) References: <1190.1393633237@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh workers Subject: Re: PATCH: make get-line widget update history number MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Mar 1, 1:20am, Oliver Kiddle wrote: } } I'm trying to think of things that this might possibly break but I } can't. I don't think I've ever used get-line before. Anyone else see a } problem? No; this looks like something that always should have been there. The only possible gotcha I can think of would be if a widget invoked from inside recursive-edit did something with "fc -p ..." without -a, or "fc -P", but I haven't really traced through what's happening with stackhist there.