On Thu, 2014-10-02 at 12:07 +0200, Ralf Corsepius wrote:
On 10/02/2014 11:25 AM, Balint Szigeti wrote:
On Thu, 2014-10-02 at 10:58 +0200, Ralf Corsepius wrote:
On 10/02/2014 10:32 AM, Balint Szigeti wrote:
hello
Don't we consider using zsh?
I'd rather not. Thoughout its history, zsh has had lots of issues originating from limitations, bugs and incompatibilities.
hm... Interesting, I and my colleague use zsh and we don't have problem with it. Can you give some examples?
Well, check autoconf's and automake's history of ca. the last 5 years. There have been a quite some patches been added to work around zsh issues ;)
One case I am currently aware about is this:
# cat script SUBDIRS="a b c" list=${SUBDIRS}; for subdir in $list; do echo $subdir done
# /bin/bash script a b c
Same result for dash and ksh, but for zsh: # /bin/zsh script a b c
Indeed. The zsh doesn't print the newline character after every entry.
I don't know about the current situation, but e.g., the configure scripts I just posted the timings of for for bash and dash fail with zsh.
Which script do you mean?
I was referring to the files I used in https://lists.fedoraproject.org/pipermail/devel/2014-October/202891.html
AFAICT so far, it fails because of behavioral difference between zsh and bash/ksh/dash outlined above (the "script" example).
Ralf