Re: PATCH: Don't store ZLE_LINE_ABORTED in vared context

[Mikael Magnusson <mikachu@xxxxxxxxx>]

On Fri, Mar 6, 2015 at 10:52 AM, Peter Stephenson
<p.stephenson@xxxxxxxxxxx> wrote:
> On Thu, 5 Mar 2015 13:58:30 +0000
> Peter Stephenson <p.stephenson@xxxxxxxxxxx> wrote:
>> On Thu, 5 Mar 2015 09:59:44 +0000
>> Peter Stephenson <p.stephenson@xxxxxxxxxxx> wrote:
>> > Having the variable set in special cases is a bit of a headache, I
>> > agree, since you don't necessarily know they're there, even if there are
>> > ways round.
>> >
>> > It would be tempting to have a different variable for the vared case
>> > such as ZLE_VARED_ABORTED.
>>
>> This would same to cover all the bases, except for the case where
>> someone really wants to use the same variable to deal with vared and the
>> shell command line.  Mikael's experience suggests that's not the most
>> obvious or convenient case.
>>...
>> +variable tt(ZLE_LINE_ABORTED).  If the editor is aborted from within
>> +tt(vared), the variable tt(ZLE_VARED_ABORTED) is set.
>
> There didn't seem to be more comments on this, and the participants
> in the discussion are certainly alive and kicking, so I've pushed it.

Oh oops, yes, meant to say this change is good with me.

-- 
Mikael Magnusson