From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11125 invoked by alias); 29 Dec 2013 06:26:56 -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: 32197 Received: (qmail 6903 invoked from network); 29 Dec 2013 06:26:40 -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: <131228222635.ZM28236@torch.brasslantern.com> Date: Sat, 28 Dec 2013 22:26:35 -0800 In-reply-to: <20131229030456.GC23678@s.lundagatan.com> Comments: In reply to Carl Drougge "[PATCH] copy-prev-shell-word broken since 4.3.11" (Dec 29, 4:04am) References: <20131229030456.GC23678@s.lundagatan.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: [PATCH] copy-prev-shell-word broken since 4.3.11 MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 29, 4:04am, Carl Drougge wrote: } Subject: [PATCH] copy-prev-shell-word broken since 4.3.11 } } I used to be able to use copy-prev-shell-word to copy the word to the } left of my cursor. At some point this broke, always giving the last } word on the line, [...] } } I have never looked at the zsh source before, but hopefully this patch } doesn't break something else. LEXFLAGS_ZLE looks quite plausible here, and it does seem to work as expected. However, I think I'm going to wait for PWS to pick this one up, as he's the originator of LEXFLAGS_*. I just noticed that, given a multiplier > 1, copy-prev-word includes the whitespace following the copied word, whereas copy-prev-shell-word does not. I don't have 4.3.10 handy to test with and 4.2.0 doesn't support using the numeric multiplier to retrieve earlier words. I think this is actually a "bug" in copy-prev-word because the whitespace is not kept when the multiplier is 1 (or not given). -- Barton E. Schaefer