From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32869-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 21254 invoked by alias); 16 Jul 2014 12:55:32 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 32869
Received: (qmail 18833 invoked from network); 16 Jul 2014 12:55:30 -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.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_NONE autolearn=ham
	version=3.3.2
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=durin42.com; h=
	mime-version:date:message-id:subject:from:to:content-type; s=
	durin42.com; bh=AHGsp3f+mm8ovH6hz8OTgTfHa04=; b=N8Htj4u8JjW3yZPh
	1l0tb+DviFwBiOkNIDb14AwWvKYL5kL07hIDcJWMR8GoEyBm8LpWmD4VqeQ8YkuG
	jxI5b6HFpDqYbeR/pUJpNCdIZ3K9joB6HI/PL/LeB/zOrZQ3lJqnweGYFxvp9wOM
	St1LnbiEtO4Xt2NodaREPjfRCUY=
MIME-Version: 1.0
X-Received: by 10.70.128.140 with SMTP id no12mr2471511pdb.147.1405514921354;
 Wed, 16 Jul 2014 05:48:41 -0700 (PDT)
Date: Wed, 16 Jul 2014 08:48:41 -0400
Message-ID: <CAPLqtWJr3LtGiqEioH0E-wje7VZi-yE6wCwkr2=r=+BK1RAoqQ@mail.gmail.com>
Subject: history-incremental-search-backward weird behavior for multiline
 commands in 5.0.x
From: Augie Fackler <raf@durin42.com>
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=001a1132ed069d309504fe4ef1ac

--001a1132ed069d309504fe4ef1ac
Content-Type: text/plain; charset=UTF-8

I upgraded my work machine from zsh 4.3.17 to zsh 5.0.5 (also tested 5.0.2
first, as that was what was in apt), and now
history-incremental-search-backward doesn't work correctly for multiline
history entries loaded from a history file on disk. As an example:

$ echo foo \
>  bar
foo bar
$ ^R bar
# finds the full command

but then in a new shell:
$ ^R bar
# finds only the word bar, not the full echo command.

This works fine in zsh 4.3.17 and zsh 4.3.11 (I get the same behavior even
if the history entry was loaded from a file).

Am I missing something obvious? setopt hist_lex_words didn't make a
difference, and I tried turning off hist_save_no_dups and
inc_append_history.

Thanks!

--001a1132ed069d309504fe4ef1ac--