Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Emulating bash
- X-seq: zsh-users 3937
- From: Mads Martin Jørgensen <mmj@xxxxxxxx>
- To: Andrej Borsenkow <Andrej.Borsenkow@xxxxxxxxxxxxxx>
- Subject: Re: Emulating bash
- Date: Sun, 24 Jun 2001 23:41:12 -0700
- Cc: zsh-users@xxxxxxxxxx
- In-reply-to: <000901c0fd3f$959bda40$21c9ca95@xxxxxxxxxxxxxx>; from Andrej.Borsenkow@xxxxxxxxxxxxxx on Mon, Jun 25, 2001 at 10:25:10AM +0400
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20010624230348.F22534@xxxxxxxx> <000901c0fd3f$959bda40$21c9ca95@xxxxxxxxxxxxxx>
* Andrej Borsenkow <Andrej.Borsenkow@xxxxxxxxxxxxxx> [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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author