zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: send-break or EOF exit the shell in "vared"
Date: Sun, 9 Feb 2020 08:33:16 +0000	[thread overview]
Message-ID: <20200209083316.axjj6nf7hndb7wqw@chazelas.org> (raw)

For context, that's still about trying to answer that "how to
add a timeout to `vared`" question at
https://unix.stackexchange.com/questions/565718/zsh-timeout-for-vared-builtin

I was thinking: vared uses zle, zle is fully programmable, that
shouldn't be too difficult. But so far I've not been able to do
it without a subshell and I ran in a few unexpected behaviours.

In:

zsh -c 'vared -c foo; echo $? $foo'

If I press ^G (send-break widget), that exits the shell (with
status 0), not just "vared".

With:

zsh -c '{ vared -c a; } always { TRY_BLOCK_ERROR=0; echo in always; }; echo $? $a'

Upon ^G, the "always" block is run, but that still exits the
shell (with status 2 this time) despite the TRY_BLOCK_ERROR=0

With:

zle-line-init() stty -icanon time 10 min 0 <&2
zle -N zle-line-init
{
  vared -c var
} always {
  TRY_BLOCK_ERROR=0
  print in always
}
echo "$? $var"


That is where a read() on the terminal will return 0 (EOF) if
nothing is entered within a second, the shell exits as well
(with status 1) not just vared, the "always" block is not run.
Same with vared -e.

My other approaches trying to use TMOUT and a SIGALRM trap or a
zle -F handler that invokes send-break or accept-line (or queues
^G/^M with zle -U) haven't been successful either (either exit
the shell or don't exit zle straight away or at all).

-- 
Stephane

             reply	other threads:[~2020-02-09  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  8:33 Stephane Chazelas [this message]
2020-02-09  9:09 ` Stephane Chazelas
2020-02-10 17:03 ` Sebastian Gniazdowski
2020-06-10  0:53 ` 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=20200209083316.axjj6nf7hndb7wqw@chazelas.org \
    --to=stephane@chazelas.org \
    --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).