zsh-workers
 help / color / mirror / code / Atom feed
From: srb@cuci.nl (Stephen R. van den Berg)
To: borsenkow.msk@sni.de,
	Zsh workers mailing list <zsh-workers@math.gatech.edu>
Subject: Re: Procmail rejects zsh as being "broken"
Date: Thu, 1 Aug 1996 13:29:46 +0200	[thread overview]
Message-ID: <199608011129.NAA17916@hera.cuci.nl> (raw)
In-Reply-To: borsenkow.msk@sni.de's message as of 1996 Aug 1 Thu 12:28. <Pine.SV4.3.95.960801121636.4508C-100000@itsrm1>

borsenkow.msk@sni.de <borsenkow.msk@sni.de> wrote:
>I recently installed procmail-3.11pre4 under zsh-3.0pre4. When running
>'make init' procmail gave me warning, that `/opt/local/bin/zsh is broken'.
>I checked initmake script and here is relevant part:

>case "$SHELL" in
> ...
>       *zsh*) $RM src/_autotst
>            $SHELL <<HERE
>            O="echo test >src/_autotst"
>            exec 2>$DEVNULL
>            \$O
>HERE                                                                            
>           if test ! -f src/_autotst 
>           then
>              echo "Warning: your $SHELL is broken, avoiding it"; SHELL=""
>           fi ;;

>The test seems to imply, that in
>% foo="echo test > test"
>% $foo

>the line is to be rescanned for I/O redirections *after* foo is expanded. 
>I am not aware of any shell to behave this way. 

You're right.  Sorry, my mistake.  The test is a bit too rigorous, it
now fails on every shell (which just had the effect that it never used
the zsh, which is why I never noticed the problem, of course).  The intent
was to check for something else.

>Do I  miss something? What is the sense of this test? And why it is done
>only for zsh ;)?

The test should have read (fixed in the next release :-):

        *zsh*) $RM src/_autotst
            $SHELL <<HERE
            O="echo test"
            exec 2>$DEVNULL 1>&2
            \$O && echo test >src/_autotst
HERE

As to why it is just being tested on zsh, well, that's the only shell
that (ever) exhibited this (broken) behaviour.
-- 
Sincerely,                                                          srb@cuci.nl
           Stephen R. van den Berg (AKA BuGless).
Auto repair rates: basic labor $40/hour; if you wait, $60; if you watch, $80;
if you ask questions, $100; if you help, $120; if you laugh, $140.


  parent reply	other threads:[~1996-08-01 13:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-01  8:28 Andrej Borsenkow
1996-08-01  8:40 ` Peter Stephenson
1996-08-01 11:29 ` Stephen R. van den Berg [this message]
1996-08-01 11:43   ` Peter Stephenson
1996-08-01 12:04     ` Zefram
1996-08-01 12:11       ` Peter Stephenson
1996-08-01 12:33         ` Zefram
1996-08-01 13:00           ` Peter Stephenson
1996-08-01 12:23     ` Stephen R. van den Berg
1996-08-01 13:02       ` Zoltan Hidvegi
1996-08-01 13:07         ` Bruce Stephens
1996-08-01 14:44         ` Stephen R. van den Berg
1996-08-01 14:59           ` Zoltan Hidvegi
1996-08-02  0:54             ` Zefram
1996-08-02  0:59           ` Zefram
1996-08-02  1:20             ` Stephen R. van den Berg

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=199608011129.NAA17916@hera.cuci.nl \
    --to=srb@cuci.nl \
    --cc=borsenkow.msk@sni.de \
    --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).