From: "Mads Martin Jørgensen" <mmj@suse.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-users@sunsite.dk
Subject: Re: Emulating bash
Date: Sun, 24 Jun 2001 23:41:12 -0700 [thread overview]
Message-ID: <20010624234112.H22534@suse.com> (raw)
In-Reply-To: <000901c0fd3f$959bda40$21c9ca95@mow.siemens.ru>; from Andrej.Borsenkow@mow.siemens.ru on Mon, Jun 25, 2001 at 10:25:10AM +0400
* Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru> [Jun 24. 2001 23:26]:
> >
> > I was toying around and beeing impressed with the bash emulation of zsh
> > (I actully moved it into /bin/bash). But it struck me it had problems
> > with trapping the signals because signals known to bash apparantly are
> > unknown to zsh-bash. This is zsh-4.0.1 final.
> >
> > Any hints to how I can fix this -- it would be nice on my small systems
> > to get zsh too :-)
> >
>
> Any hints what your particular problem is? :-) It is hard to fix without
> knowing what to fix - and not every zsh user or worker expert in bash.
>
> What signals are in bash?
Of course -- totally forgot.
It is when trapping SIGINT and SIGTERM, it says unknown signal. SIGQUIT
and SIGSEGV are not problematic..
_From the bash manual (2.05):
SIGNALS
When bash is interactive, in the absence of any traps, it
ignores SIGTERM (so that kill 0 does not kill an interac
tive shell), and SIGINT is caught and handled (so that the
wait builtin is interruptible). In all cases, bash
ignores SIGQUIT. If job control is in effect, bash
ignores SIGTTIN, SIGTTOU, and SIGTSTP.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic and
totally illogic, with just a little bit more effort."
-- A. P. J.
next prev parent reply other threads:[~2001-06-25 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 6:03 Mads Martin Jørgensen
2001-06-25 6:25 ` Andrej Borsenkow
2001-06-25 6:41 ` Mads Martin Jørgensen [this message]
2001-06-25 6:54 ` Andrej Borsenkow
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=20010624234112.H22534@suse.com \
--to=mmj@suse.com \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-users@sunsite.dk \
/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).