zsh-workers
 help / color / mirror / code / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Richard Hartmann <richih.mailinglist@gmail.com>,
	david sowerby <d_sowerby@yahoo.com>,
	 zsh-workers@sunsite.dk
Subject: Re: select problem
Date: Sun, 18 Jan 2009 16:45:42 +0100	[thread overview]
Message-ID: <2d460de70901180745t6e4307eftebec766618f6c1b1@mail.gmail.com> (raw)
In-Reply-To: <20090118143905.GA4898@sc.homeunix.net>

On Sun, Jan 18, 2009 at 15:39, Stephane Chazelas
<Stephane_Chazelas@yahoo.fr> wrote:

> Still, I can't think of how a script could be reasonably made to
> rely on that behavior, which is why it's not a problem that all
> shells break POSIX conformance there, in a same way that running
> a POSIX script with zsh (in sh emulation) generally isn't a
> problem because it's only in corner cases that zsh is not
> conformant.

Having symlinked zsh to /bin/sh for some time on my system,
I have to say it's a quick way to make your Debian system
stop working. Grml had a similar experience which is why
they went back to Bash.


> When a POSIX conformance issue is found by someone,
> it is generally raised on this mailing list and most of the time
> fixed (at least in sh emulation).

Afaik, there are several issues open. If there is any interest,
I can try to round them up so they can be shot.


> Having said that, I agree there's no much point of having zsh as
> your POSIX sh.

AFAIK, that is the official stance.


Richard


  reply	other threads:[~2009-01-18 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:48 david sowerby
2009-01-17  7:12 ` Andrey Borzenkov
2009-01-17  9:25 ` Stephane Chazelas
2009-01-17 11:21   ` Richard Hartmann
2009-01-18 14:39     ` Stephane Chazelas
2009-01-18 15:45       ` Richard Hartmann [this message]
2009-01-20 19:42         ` Peter Stephenson
2009-01-20 21:30           ` Richard Hartmann

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=2d460de70901180745t6e4307eftebec766618f6c1b1@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=d_sowerby@yahoo.com \
    --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).