From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: coleman@math.gatech.edu (Richard Coleman)
Cc: zsh-workers@math.gatech.edu
Subject: Re: BSD_ECHO
Date: Thu, 15 Aug 1996 02:32:24 +0200 (MET DST) [thread overview]
Message-ID: <199608150032.CAA09479@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199608142045.QAA00597@redwood.skiles.gatech.edu> from Richard Coleman at "Aug 14, 96 04:45:31 pm"
Richard wrote:
[...]
> > I still object to having a configure test for the default behavior of
> > BSD_ECHO when run as "sh". This should NOT be something that varies
> > from one installation to the next!
[...]
> I completely agree...
>
> The options for zsh when called as sh, should not depend on
> your current configuration. It is especially bad for us sysadmins
> who work on heterogenous environments.... I don't want zsh working
> one way on one machine, and another way on another machine.
Seing the big opposition I'll remove that configure check. However this
was not a completely unreasonable change. I use zsh as /bin/sh on Linux
where the default /bin/sh is bash. I bet that without BSD_ECHO some
scripts will break.
On the other hand someone else reported that on an other system zsh broke
some scripts because of BSD_ECHO. It is possible to turn on BSD_ECHO iff
zsh is invoked as /bin/sh (with full pathname) and configure detected that
/bin/sh use BSD_ECHO but it would not be set by emulate or alternatively is
would be always set or unset by emulate. On systems where zsh is installed
as /bin/sh the system administrator probably knows enough about how to set
the desired default and others won't be affected by this change.
I know that prefect solution is not possible. Even POSIX did not dare to
define the default echo behaviour. If one wants to write a portable script
it must begin with something like #! /usr/local/bin/zsh -f. We have 7
different OS'es in an NFS/NIS network where zsh is very useful as portable
script language (and as a login shell of course).
Zoltan
next prev parent reply other threads:[~1996-08-15 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-14 17:15 Final 3.0.0 test release Zoltan Hidvegi
1996-08-14 17:47 ` Richard Coleman
1996-08-14 18:11 ` Bart Schaefer
1996-08-14 20:45 ` Richard Coleman
1996-08-15 0:32 ` Zoltan Hidvegi [this message]
1996-08-15 0:39 ` Zoltan Hidvegi
1996-08-14 19:09 ` Steven L Baur
1996-08-15 0:43 ` Zoltan Hidvegi
1996-08-15 1:14 ` Steven L Baur
1996-08-15 5:25 ` Mark Borges
1996-08-15 15:29 ` Steven L Baur
1996-08-15 6:52 ` Marc Martinez
1996-08-15 10:38 ` Zoltan Hidvegi
1996-08-14 23:47 BSD_ECHO Zefram
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=199608150032.CAA09479@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=coleman@math.gatech.edu \
--cc=zsh-workers@math.gatech.edu \
/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).