zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <schizo@debian.org>
To: Christophe Martin <schplurtz@free.fr>
Cc: 310872@bugs.debian.org, zsh-workers@sunsite.dk
Subject: Re: Bug#310872: zsh can't be a ksh replacement (can't trap ERR).
Date: Mon, 30 May 2005 10:06:16 -0400	[thread overview]
Message-ID: <20050530140616.GA7651@scowler.net> (raw)
In-Reply-To: <42971781.9050402@free.fr>

> Why not add ash, dash, bash and so on, into the ksh pool, until
> only "a=foo" and "echo bar" are the common points ? surely because
> all of us have an idea of what ksh should be, only this idea is a
> bit different for each of us.

None of those shells purport to emulate ksh.  zsh does.

> I realize there are many differences between implementations of
> shells. There must be some incompatibilities between pdksh and ksh.
> But this trap ERR thing seems to be a basic ksh functionnality.

I don't have enough knowledge of ksh to evaluate that statement.

> Last, zsh is such a special shell, with all its exotic and powerful
> functionalities, that when you need/want it, it is unlikely
> you want it as a ksh. Debian already have 2 ksh...

The zsh alternative was suggested by the Debian ksh93
maintainer.

> I definitely hope that the alternative will be removed...

It's not a high-priority alternative.  That means that it won't be
selected automatically over either pdksh or ksh93.  One would need
to either only have zsh installed or override the defaults.  Since
the Debian zsh package is frozen for a June 6 release, the severity
of your problem will not justify a change to the package.

After that, we can do one of three things: leave things the way they
are; remove the alternative; patch the source or cause zsh to understand
the ERR pseudo-signal within ksh emulation in another manner.

If the wise people on zsh-workers think that not understanding ERR is
acceptable for ksh emulation, I'm inclined to do nothing.


  reply	other threads:[~2005-05-30 14:06 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
2005-05-27 16:34         ` Christophe Martin
2005-05-27 12:50   ` Christophe Martin
2005-05-30 14:06     ` Clint Adams [this message]
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=20050530140616.GA7651@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).