From: Clint Adams <schizo@debian.org>
To: Christophe Martin <schplurtz@free.fr>, 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: Thu, 26 May 2005 15:15:20 -0400 [thread overview]
Message-ID: <20050526191520.GA30061@scowler.net> (raw)
In-Reply-To: <200505261638.SAA09610@sdt.univ-brest.fr>
> This is very simple. zsh is not to be considered a ksh.
> This simple command fails using zsh as ksh (I did update-alternatives) :
>
> trap 'echo alert-an-error-occured' ERR
>
> This simple command succeeds with `normal/standard' ksh, tested with :
> Solaris ksh,
> OSF1 ksh,
> AIX ksh,
> pdksh (debian sarge),
> www.kornshell.com ksh.
>
> I hope you will remove this alternative before too many scripts break...
Recently, the Debian packages for ksh93, pdksh, and zsh cooperated to
provide alternatives for /bin/ksh. This was done without defining any
exact requirements, so at the present time, it is de facto "the
intersection of ksh93, pdksh, and zsh".
Unless this bug is deemed release-critical (I doubt it will be), the
upcoming Debian release will allow zsh to easily be /bin/ksh.
P.S., someone left conflict cruft in ChangeLog.
next parent reply other threads:[~2005-05-26 19:15 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 [this message]
2005-05-27 1:20 ` Bart Schaefer
2005-05-27 12:50 ` Christophe Martin
2005-05-27 14:19 ` Bart Schaefer
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=20050526191520.GA30061@scowler.net \
--to=schizo@debian.org \
--cc=310872@bugs.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).