From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-request@euclid.skiles.gatech.edu>
Received: (qmail 403 invoked from network); 30 Dec 1996 04:11:06 -0000
Received: from euclid.skiles.gatech.edu (list@130.207.146.50)
  by coral.primenet.com.au with SMTP; 30 Dec 1996 04:11:06 -0000
Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id WAA17416; Sun, 29 Dec 1996 22:53:04 -0500 (EST)
Resent-Date: Sun, 29 Dec 1996 22:36:19 -0500 (EST)
Date: Mon, 30 Dec 1996 04:37:24 +0100 (MET)
From: Wolfgang Hukriede <whukriede@ifm.uni-kiel.de>
Message-Id: <199612300337.EAA11748@sally.ifm.uni-kiel.de>
To: zsh-users@math.gatech.edu
Subject: Re: bug in select
Resent-Message-ID: <"m9XxC1.0.aA4.oYpno"@euclid>
Resent-From: zsh-users@math.gatech.edu
X-Mailing-List: <zsh-users@math.gatech.edu> archive/latest/569
X-Loop: zsh-users@math.gatech.edu
X-Loop: zsh-workers@math.gatech.edu
Precedence: list
Resent-Sender: zsh-workers-request@math.gatech.edu


>>    verdy% select i in aaa bbb ccc
>>    do echo $i
>>    done
>>    1) aaa  2) bbb  3) ccc
>>    ?# 1
>>    0

Zoltan wrote:

>Ksh behaves exactly the same way.  This is not a bug.  Add unset i before
>select and it'll work.  Note that i becomes integer if it is initialised
>first in an arithmetic expression, like let i=0 or $((i=0)).

Yes, and in the same spirit:

        zsh> i="something"; echo $i
        0

etc. (If the variable is by any accident integer.) That's hazard. The shell
should print out a message, imo. These are type errors.

Wolfgang.