Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!hellgate.utah.edu!helios.ee.lbl.gov!pasteur!ucbvax!hplabs!hpfcso!hpfelg!koren
From: koren@hpfelg.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.tech
Subject: Re: What should be in future SKsh versions?
Message-ID: <13920028@hpfelg.HP.COM>
Date: 11 Dec 89 15:20:50 GMT
References: <13920018@hpfelg.HP.COM>
Organization: HP Elec. Design Div. -FtCollins
Lines: 44

> Since I only have ASH (haven't been able to find SKsh yet, where is
> it?) I found two things (so far) I would like to see SKsh do. It might

Yup, 1.2 is very much more stable than either of the Ash versions.  1.3 will
probably be appearing in around a month or so (sometime after the holiday
season winds down) and it has the largest list of enhancements and fixes
yet.

> 1)  In sh/ksh I can do this:

> 	FILES=(one.txt two.txt three.txt)
> 	for i in $FILES

Well, you can can do it in Sksh, but you have to use quotes instead of
parens:

        FILES='one.txt two.txt three.txt'
        for i in $FILES

That will work, although it depends on the setting of $IFS.
    
>     FILES=(dh0:man/*)

try:

       for i in dh0:man/*

or,
       FILES=$(echo dh0:man/*)
       for i in FILES

> The shell should beep indicating I have multiple choices. In addition
> if I hit <CTRL-D> it should list my possible choices as:
> 
	> amiga.txt.1 	amy.list

In Sksh (1.2), you can list the possible choices by using <esc>-=.  (This
is the same keystroke that ksh uses).  Also, <esc>-* is supported.

> Forgive my rambling, but this is my wishlist.

 Most of it is accomplishable(??) in 1.2.

      - steve