From: Bart Schaefer <email@example.com>
Cc: Zsh Users <firstname.lastname@example.org>
Subject: Re: Trapping Real Time Signals in ZSH
Date: Fri, 23 Jul 2021 13:41:39 -0700 [thread overview]
Message-ID: <CAH+w=7b_r0MMftDbe4qP12ewNqLywd0nETAMNx8o3D4uXyY3pQ@mail.gmail.com> (raw)
On Wed, Jul 21, 2021 at 7:31 PM <email@example.com> wrote:
> In bash the trap builtin is able to handle all signals including SRTMIN-
> SIGRTMAX. In ZSH the kill builtin dos not provide the ability to utilize all
> of there signals. Is there any supported way to handle trapping real-time
> signals in ZSH?
Currently there is not. The scripts in the build process that extract
signal names from the system headers do not recognize SIGRTMIN or or
SIGRTMAX, and the faux signals SIGZERR and SIGDEBUG may overlap with
the range of realtime signals.
However, it's possible to send any of these signals by number with the
kill builtin, even though "kill -l" doesn't list them.
prev parent reply other threads:[~2021-07-23 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 2:30 bagnaramatt
2021-07-23 20:41 ` Bart Schaefer [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).