From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2822 invoked by alias); 25 Jan 2015 21:32:22 -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: 34396 Received: (qmail 839 invoked from network); 25 Jan 2015 21:32:20 -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=G9TTV+Wwq+KGR9WR3wC5dVTyu8spfxHkQkJ200OOEvQ=; b=ddMw4biBJmGPw9d5QA5n3bq8+V7/a/fhS2qy6Ot2Vhj9bQnmIo1V9WNpWiPuaTyOUc aqy+kg9ANUHgrXvrKjpE26OJ0w/JMKthh2jI2TJ+XImqYleA7MDBEm4xs7Y9LsgZzi6g IqqMcOmqCzLluHs8mcr64Z8nE1grqjxttdUom9SuRrWgVdj4NdNEyfvsvPKpHKZcJIoA fR1rVus6422fPXIcNxjmkaQHrUMDwLdOQ/l4Gkq0sIITcjDxvGkNr2GYz4/NKkZ5ByHU TsI5RLyKNU0abQxCT5wHpBOBwUPlPovmp0x5PyPcFBnFXa8qUfd1GeEi6PMF+Bb4QyDM TDrA== MIME-Version: 1.0 X-Received: by 10.42.76.135 with SMTP id e7mr18467052ick.46.1422221538750; Sun, 25 Jan 2015 13:32:18 -0800 (PST) In-Reply-To: <150125131515.ZM31850@torch.brasslantern.com> References: <150125115905.ZM31435@torch.brasslantern.com> <150125131515.ZM31850@torch.brasslantern.com> Date: Sun, 25 Jan 2015 22:32:18 +0100 Message-ID: Subject: Re: histlexwords error with >! token From: Mikael Magnusson To: Bart Schaefer Cc: zsh workers Content-Type: text/plain; charset=UTF-8 On Sun, Jan 25, 2015 at 10:15 PM, Bart Schaefer wrote: > On Jan 25, 9:40pm, Mikael Magnusson wrote: > } > } > - wptr++; > } > + if (!*++wptr) > } > + break; > } > } That appears to do the trick. I also tried recalling the words with > } insert-last-word and copy-earlier-word and they show up as expected > } even when they contain spaces, which wasn't the case before the patch. > > Hm, that's a little strange (unless you mean this happens on lines that > also contain ">!") -- for the simple case of words containing a space, > the strpfx() call up at line 3407 should have done the trick in the > first place. > > Nevertheless, I'll go ahead and push this for now. Yes, I'm talking about a line that has >! on it. Without the patch, recalling words gives you 'foo\' and 'bar' separately instead of a single 'foo\ bar'. What I meant by pointing that out in the first place is that stuff is actually working, we didn't just suppress an error message :). -- Mikael Magnusson