From: Bart Schaefer <schaefer@brasslantern.com>
To: Christophe Martin <schplurtz@free.fr>,
Clint Adams <schizo@debian.org>,
310872@bugs.debian.org
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#310872: zsh can't be a ksh replacement (can't trap ERR).
Date: Fri, 27 May 2005 14:19:06 +0000 [thread overview]
Message-ID: <1050527141906.ZM21908@candle.brasslantern.com> (raw)
In-Reply-To: <42971795.8090005@free.fr>
On May 27, 2:50pm, Christophe Martin wrote:
} Subject: Re: Bug#310872: zsh can't be a ksh replacement (can't trap ERR).
}
} Bart Schaefer a écrit :
} >
} > A possible workaround would be
} >
} > (( $signals[(I)ERR] )) || alias -g ERR=ZERR
}
} But, If i keep zsh as ksh
} I have to rewrite every script to put this workaround in.
No, you just have to put the above in /etc/zshenv, which is read by all
instances of zsh, whether script or interactive.
} So, for this particular problem of trap ERR, there are only problems
} in using zsh as a ksh
That's not the only incompatibility, by a long shot. Don't try scripts
using namerefs or discipline functions, for example.
} (By the way, what are the platform with OS
} SIGERR ? And do some ksh run on them ?)
UNICOS, according to the Zsh FAQ. I have no idea whether ksh has been
ported to that.
next prev parent reply other threads:[~2005-05-27 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505261638.SAA09610@sdt.univ-brest.fr>
2005-05-26 19:15 ` Clint Adams
2005-05-27 1:20 ` Bart Schaefer
2005-05-27 12:50 ` Christophe Martin
2005-05-27 14:19 ` Bart Schaefer [this message]
2005-05-27 16:34 ` Christophe Martin
2005-05-27 12:50 ` Christophe Martin
2005-05-30 14:06 ` Clint Adams
2005-05-30 18:41 ` Bart Schaefer
2005-06-01 8:25 ` Oliver Kiddle
2005-06-01 10:31 ` Peter Stephenson
2005-06-01 13:50 ` Bart Schaefer
2005-06-01 13:57 ` Bart Schaefer
2005-06-01 14:04 ` Peter Stephenson
2005-06-01 14:09 ` 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=1050527141906.ZM21908@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=310872@bugs.debian.org \
--cc=schizo@debian.org \
--cc=schplurtz@free.fr \
--cc=zsh-workers@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).