From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH: Don't store ZLE_LINE_ABORTED in vared context
Date: Fri, 6 Mar 2015 17:05:50 +0100 [thread overview]
Message-ID: <CAHYJk3RdMfBptc1jr3O_cBdybxhMKBXbeUZ2yf50zz7y0mQPiw@mail.gmail.com> (raw)
In-Reply-To: <20150306095233.2db3d7f9@pwslap01u.europe.root.pri>
On Fri, Mar 6, 2015 at 10:52 AM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Thu, 5 Mar 2015 13:58:30 +0000
> Peter Stephenson <p.stephenson@samsung.com> wrote:
>> On Thu, 5 Mar 2015 09:59:44 +0000
>> Peter Stephenson <p.stephenson@samsung.com> 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
prev parent reply other threads:[~2015-03-06 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:40 Mikael Magnusson
2015-03-05 1:57 ` Bart Schaefer
2015-03-05 2:41 ` Mikael Magnusson
2015-03-05 4:46 ` Bart Schaefer
2015-03-05 9:59 ` Peter Stephenson
2015-03-05 13:58 ` Peter Stephenson
2015-03-06 9:52 ` Peter Stephenson
2015-03-06 16:05 ` Mikael Magnusson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHYJk3RdMfBptc1jr3O_cBdybxhMKBXbeUZ2yf50zz7y0mQPiw@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).