From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function)
Date: Tue, 27 Apr 2021 13:46:12 +0300 [thread overview]
Message-ID: <CAHLkEDtgMYYVdtHBiPDYbhdhwRH9Ha3T1ix+G_q_=-miNgo=PA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZDorYi2C+0ycysL=99nh_6Mw865H4kB6ZYaHmMZr9tNA@mail.gmail.com>
On Tue, Apr 27, 2021 at 12:40 AM Bart Schaefer
<schaefer@brasslantern.com> wrote:
> I would think that occurs with "zle .push-line-or-edit" also?
>
> Anyway, no, there's no way to abort the current ZLE without $?
> becoming nonzero. A lot of effort was put into preserving the value
> of $? across everything that comes in between the previous command
> ending (even if it ended by interrupting ZLE) and the next prompt
> being printed.
>
> I believe you'll see similar things with e.g. edit-command-line from
> the distribution, if it happens to take the branch that calls
> send-break.
In my patch, the last thing done before the widget exits is to set
$BUFFER and call zle .accept-line. The only return value the user will
see in that case is that of the executed command; not that of
.push-line-or-edit. I still prefer that version. Are there drawbacks
to that approach?
next prev parent reply other threads:[~2021-04-27 10:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 13:36 [RFC][PATCH] Add change-directory() widget function Marlon Richert
2021-04-20 19:43 ` Bart Schaefer
2021-04-20 20:13 ` Marlon Richert
2021-04-20 21:32 ` Bart Schaefer
2021-04-21 3:46 ` Bart Schaefer
2021-04-21 11:37 ` [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function) Marlon Richert
2021-04-21 20:40 ` Bart Schaefer
2021-04-21 21:27 ` Daniel Shahaf
2021-04-21 21:58 ` Bart Schaefer
2021-04-22 10:55 ` Marlon Richert
2021-04-22 20:25 ` Daniel Shahaf
2021-04-22 23:27 ` Bart Schaefer
2021-04-24 20:06 ` Marlon Richert
2021-04-24 21:49 ` Bart Schaefer
2021-04-24 21:58 ` Bart Schaefer
2021-04-26 18:08 ` Marlon Richert
2021-04-26 21:39 ` Bart Schaefer
2021-04-27 10:46 ` Marlon Richert [this message]
2021-04-27 19:27 ` Bart Schaefer
2021-04-30 19:16 ` Marlon Richert
2021-04-30 20:25 ` Bart Schaefer
2021-05-01 13:30 ` Marlon Richert
2021-05-31 17:55 ` Marlon Richert
2021-04-25 17:02 ` Hard-wrapping emails (Was: [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function)) Lawrence Velázquez
2021-04-20 21:57 ` [RFC][PATCH] Add change-directory() widget function Daniel Shahaf
2021-04-20 22:14 ` Daniel Shahaf
2021-04-21 0:09 ` Bart Schaefer
2021-04-21 3:18 ` Bart Schaefer
2021-04-21 20:11 ` Daniel Shahaf
2021-04-21 20:29 ` Bart Schaefer
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='CAHLkEDtgMYYVdtHBiPDYbhdhwRH9Ha3T1ix+G_q_=-miNgo=PA@mail.gmail.com' \
--to=marlon.richert@gmail.com \
--cc=schaefer@brasslantern.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).