From: Dennis Schwartz <dennis.schwartz@protonmail.com>
To: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: TRAPINT doesn't work reliably
Date: Tue, 17 Sep 2019 16:47:43 +0000 [thread overview]
Message-ID: <XwKNAg1qGlWEVe6teZMU0FhD554sBKMAVDblWDoIFxZeOktj1B6qY4Jl7BESBBQFtRKy8SeAa7UzBcB5vShOqFQTgNcZoWShxyjeLaLrCKI=@protonmail.com> (raw)
Hi,
I have a function on TRAPINT in my .zshrc like described as in the Zsh manual [1].
TRAPINT() {
echo "trap: $1"
return $(( 128 + $1 ))
}
This works unreliably. Usually this works a first few times, but after a while this doesn’t work anymore and throws the following error.
TRAPINT:1: command not found: \M-^A^A
TRAPINT:2: command not found: F^\V
This command used to work flawlessly in Zsh 5.3.1 (Debian strech). I only encounter this issue in 5.7.1.
Is this a regression that might have been introduced, or is there maybe something else wrong in my (other) configuration?
Thanks,
Dennis
[1] http://zsh.sourceforge.net/Doc/Release/Functions.html#index-trapping-signals
next reply other threads:[~2019-09-17 16:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190917164905epcas1p4ad458ffcd504501780d522880c81de3e@epcas1p4.samsung.com>
2019-09-17 16:47 ` Dennis Schwartz [this message]
2019-09-24 8:44 ` Peter Stephenson
2019-09-25 13:02 ` Dennis Schwartz
2019-09-25 14:01 ` Peter Stephenson
2019-09-25 16:25 ` Dennis Schwartz
2019-09-25 17:04 ` Peter Stephenson
2019-09-25 18:46 ` Daniel Shahaf
2019-09-26 15:27 ` Peter Stephenson
2019-09-27 13:43 ` Daniel Shahaf
2019-09-25 17:56 ` Peter Stephenson
2019-09-26 14:48 ` Dennis Schwartz
2019-09-26 15:25 ` Peter Stephenson
2019-09-26 17:10 ` Dennis Schwartz
2019-09-27 13:46 ` Daniel Shahaf
2019-09-28 11:16 ` Dennis Schwartz
2019-09-28 14:29 ` Daniel Shahaf
2019-09-28 18:21 ` Dennis Schwartz
2019-09-28 18:58 ` Dennis Schwartz
2019-09-28 16:00 ` Bart Schaefer
2019-09-29 16:54 ` Peter Stephenson
2019-09-27 19:05 ` Peter Stephenson
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='XwKNAg1qGlWEVe6teZMU0FhD554sBKMAVDblWDoIFxZeOktj1B6qY4Jl7BESBBQFtRKy8SeAa7UzBcB5vShOqFQTgNcZoWShxyjeLaLrCKI=@protonmail.com' \
--to=dennis.schwartz@protonmail.com \
--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).