From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: A POSIX and a UTF-8 question
Date: Mon, 11 Sep 2006 18:05:34 +0100 [thread overview]
Message-ID: <200609111705.k8BH5Yfo016012@news01.csr.com> (raw)
In-Reply-To: <20060911163950.59225.qmail@web36812.mail.mud.yahoo.com>
Daniel Qarras wrote:
> 1) There is unfortunately a bash-only expression used in RH's shell
> function library, that is =~. However, this was used only once in
> device mapper related function so that did not affect me, I just
> commented it out. YMMV. (I did not find a www description for this but
> it can be at least checked from bash3.1 manual pages what it does.
That's for extended regular expressions. That wouldn't be too hard to
support, if we used the system's RE capabilities, although we'd probably
want to do parentheses differently. However, as you say, it's specific
to bash so isn't that vital.
> 2) It seems that many RH scripts do something like:
>
> cd /some/path
> . functions
>
> and in zsh-4.3 as /bin/sh this does not work, it needs to be:
>
> cd /some/path
> . ./functions
Right. I think zsh has always been implemented like that. We don't
really want to change it; the standard (IEEE Std 1003.1, 2004 Edition)
says specifically:
RATIONALE
Some older implementations searched the current directory for the
file, even if the value of PATH disallowed it. This behavior was
omitted from this volume of IEEE Std 1003.1-2001 due to concerns
about introducing the susceptibility to trojan horses that the user
might be trying to avoid by leaving dot out of PATH .
I checked on my Fedora system (about Core 4, I think) and the only init
script without a path is network:
cd /etc/sysconfig/network-scripts
. network-functions
If it's still there it probably ought to be fixed.
> Additionally, there's one cosmetic bash feature used that seems to be
> not supported by zsh: RH uses in their i18n effort tricks like:
>
> echo -n $"Starting service foo: "
It would be relatively easy to interpret these in the same fashion as
some other form of quoting. However, there's not much
internationalization in these parts and won't be without a huge effort
and it's not clear it's worth the effort doing anything apart from that.
Thanks for the notes.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
next prev parent reply other threads:[~2006-09-11 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 20:23 Daniel Qarras
2006-09-04 21:11 ` Bart Schaefer
2006-09-04 23:16 ` Clint Adams
2006-09-05 18:23 ` Daniel Qarras
2006-09-07 18:03 ` Peter Stephenson
2006-09-11 16:39 ` Daniel Qarras
2006-09-11 17:05 ` Peter Stephenson [this message]
2006-09-11 17:37 ` Daniel Qarras
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=200609111705.k8BH5Yfo016012@news01.csr.com \
--to=pws@csr.com \
--cc=zsh-users@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).