From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: edit-command-line breaks out of vared
Date: Mon, 20 Aug 2018 12:58:32 +0000 [thread overview]
Message-ID: <1534769912.102537.1479915000.00485AFF@webmail.messagingengine.com> (raw)
In-Reply-To: <CAH+w=7aL3yswgM36XU_ehwa5ppH0zXw4qxCgCLiOwKRBH3XbnA@mail.gmail.com>
Bart Schaefer wrote on Sun, 19 Aug 2018 12:03 -0700:
> > On Sun, Aug 19, 2018 at 2:22 PM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >>
> >> I expected quitting the editor to let me resume the vared session
>
> My first inclination here is to ask why you expected that ...
>
> >> instead it left me with the variable's value as a command line.
>
> ... because the name of the function is edit-command-line, after all.
>
I assumed edit-command-line would work inside vared, despite the
name, and that when $EDITOR finished it would return me to the
previous context.
> On Sun, Aug 19, 2018 at 6:18 AM, Mikael Magnusson <mikachu@gmail.com> wrote:
> > This works in my version of edit-command-line,
> >
> > + [[ -z $PREBUFFER ]] && {
>
> Hrm, is PREBUFFER really guaranteed to be empty whenever vared is
> running? I suppose so.
Is there a reason not to commit that? Before we might've thought it was only
an optimisation but now it seems to enable behaviour that isn't possible with
the code in HEAD. I don't see anything in my archives about reasons not to
commit that.
Cheers,
Daniel
next prev parent reply other threads:[~2018-08-20 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 12:22 Daniel Shahaf
2018-08-19 13:18 ` Mikael Magnusson
2018-08-19 19:03 ` Bart Schaefer
2018-08-20 12:58 ` Daniel Shahaf [this message]
2020-08-05 11:12 ` Mikael Magnusson
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=1534769912.102537.1479915000.00485AFF@webmail.messagingengine.com \
--to=d.s@daniel.shahaf.name \
--cc=zsh-users@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).