From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: The curious incident of the feep in the night-time
Date: Sun, 2 May 2021 15:20:35 -0700 [thread overview]
Message-ID: <CAH+w=7ZvGsbBoFpnJTb4weWPRv+HB63BhA9h27rTr0mZvhKUWg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7baQBZh1Dfse1pC0GZSdqoEesJfVrCVHFKZqs5v1po4rA@mail.gmail.com>
On Thu, Apr 29, 2021 at 11:27 AM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> An actual interrupt signal causes getbyte() to behave as if no
> keystroke were entered [...], sendbreak() eventually returns
> whatever keystroke(s) initiated the widget
More accurately, on sendbreak() the keystrokes have already been
returned, and used to select the widget.
This brings us to the final (I hope) complication, which is that when
a built-in widget is run by execzlefunc() any result stored in lastval
is retained, whereas invoking a user-defined widget passes noreturnval
= 1 to doshfunc() which causes lastval to be overwritten by the saved
value from before the function was invoked. This spoils a scheme I
briefly considered wherein running
zle send-break 75
(for example) would cause $? to be set to 75. I suppose it's best to
drop that idea and leave noreturnval as it is, because as it happens
there are no builtin widgets that change lastval.
A question for anyone still following this: Is it acceptable/desirable that
{ zle send-break } always {
TRY_BLOCK_ERROR=0
TRY_BLOCK_INTERRUPT=0
}
causes the send-break to be disregarded? Or should send-break in fact
have its own not-clearable state?
prev parent reply other threads:[~2021-05-02 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 21:35 Bart Schaefer
2021-04-28 7:26 ` Stephane Chazelas
2021-04-28 18:15 ` Bart Schaefer
2021-04-29 1:04 ` Bart Schaefer
2021-04-29 18:27 ` Bart Schaefer
2021-05-02 22:20 ` Bart Schaefer [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='CAH+w=7ZvGsbBoFpnJTb4weWPRv+HB63BhA9h27rTr0mZvhKUWg@mail.gmail.com' \
--to=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).