From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-32888-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 10014 invoked by alias); 18 Jul 2014 18:27:17 -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: 32888
Received: (qmail 11063 invoked from network); 18 Jul 2014 18:27:04 -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
X-Originating-IP: [86.6.157.246]
X-Spam: 0
X-Authority: v=2.1 cv=bPyYIZOZ c=1 sm=1 tr=0 a=BvYiZ/UW0Fmn8Wufq9dPrg==:117
 a=BvYiZ/UW0Fmn8Wufq9dPrg==:17 a=NLZqzBF-AAAA:8 a=ngHcUYYLvfkA:10
 a=uObrxnre4hsA:10 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=jYbpTv2ewKmLKwpDBK4A:9
 a=CjuIK1q_8ugA:10 a=I6wTmPyJxzYA:10
Date: Fri, 18 Jul 2014 19:21:31 +0100
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Fix loading of multi-line history entires from disk
Message-ID: <20140718192131.24516ff4@pws-pc.ntlworld.com>
In-Reply-To: <140717200824.ZM4640@torch.brasslantern.com>
References: <201407171958.s6HJwj5f003940@pws-pc.ntlworld.com>
	<140717200824.ZM4640@torch.brasslantern.com>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 17 Jul 2014 20:08:24 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> } Is it worth appending something syntactically null but a little more
> } complicated that we can strip on input with little likelihood of
> } stepping on anyone's toes?  " ; "?   Unless we do attempt that, appending
> } a simple space is as good as anything.
> 
> We could follow the examples of extended-history and _complete_debug to
> use something that begins with ";:".
> 
> E.g. we could do something like ";: ENDS_WITH_BACKSLASH" but that's not
> really "syntactically null" though it is semantically null.

I think we need something that works without extended-history on,
though, and even though we can still read it in specially if it's like
that it kind of violates the spirit.