From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32872-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 10296 invoked by alias); 16 Jul 2014 16:41:09 -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: 32872
Received: (qmail 3099 invoked from network); 16 Jul 2014 16:41:05 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7f626d000004b39-52-53c6a8c14523
Date: Wed, 16 Jul 2014 17:30:56 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: history-incremental-search-backward weird behavior for multiline
 commands in 5.0.x
Message-id: <20140716173056.6515047e@pwslap01u.europe.root.pri>
In-reply-to: <140716091007.ZM2526@torch.brasslantern.com>
References:
 <CAPLqtWJr3LtGiqEioH0E-wje7VZi-yE6wCwkr2=r=+BK1RAoqQ@mail.gmail.com>
 <140716091007.ZM2526@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFuphluLIzCtJLcpLzFFi42I5/e/4Nd2DK44FG1w+LGtxsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4MtZeamcv+MRasfb3UbYGxkMsXYycHBICJhKnZ/yFssUkLtxb
	z9bFyMUhJLCUUWLCjPXMIAkhgeVMEmc3BYDYLAKqEs9e9bGC2GwChhJTN81mBLFFBMQlzq49
	DzSIg0NYIFFiVk8lSJhXwF7iwum7YGM4BSwlJv4GKQGZ38gosXZnNxNIgl9AX+Lq309MEEfY
	S8y8coYRollQ4sfke2DHMQtoSWze1sQKYctLbF7zlnkCo8AsJGWzkJTNQlK2gJF5FaNoamly
	QXFSeq6RXnFibnFpXrpecn7uJkZICH7dwbj0mNUhRgEORiUeXobZR4OFWBPLiitzDzFKcDAr
	ifBOm3UsWIg3JbGyKrUoP76oNCe1+BAjEwenVANj1nYu9ZKPbX8373A5da89pWLHGqbtl7cz
	Blrk65+YVWmvda/r3CH2tRsr2I4llj5fU3fgwNnpDV8cF7VPYyrurZJa/nVSWeK8c4dsZH6u
	+jzx0lmdhzYl/17s+DTD88hj4aOWSnOFzC+/nmt24VltukCWxqbJ0X473F5F77ZgOP3ptsi2
	Pd/CqpVYijMSDbWYi4oTAc+vT64fAgAA

On Wed, 16 Jul 2014 09:10:07 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> Hmm, it looks like history loading may be mis-handling the case of an
> INTENTIONAL backslash-newline pair.  This gets stored in the history
> file as e.g.
> 
> echo foo \\
>  bar
> 
> This is then re-loaded as the two lines
> 
> echo foo \\
> 
> (note the backslash is still doubled, though it was not when it was
> originally input) and
> 
>  bar
> 
> which obviously is wrong.  I'm not sure whether the fix is to store
> it with three backslashes, or to parse it differently on load, or both.

I think the load parsing must be broken --- I'm pretty sure it always
used doubled backslashes to signal this and it obviously used to work.

pws