Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpfcso!hpfcdc!koren
From: koren@hpfcdc.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.misc
Subject: Re: SKsh variables
Message-ID: <37090007@hpfcdc.HP.COM>
Date: 29 Mar 91 18:28:03 GMT
References: <6765@khaki14.UUCP>
Organization: HP Fort Collins, Co.
Lines: 37


> |What am I doing wrong?  I can successfully assign other non-environment
> |variables, just have problems with these startup ones.

Are you typing this in from the keyboard, putting it in your .skshrc,
or what?  This works fine in 1.6, so I recommend you upgrade:

[ram:]: echo $HOME
SYS:
[ram:]: HOME=ram:
[ram:]: echo $HOME
ram:
[ram:]: version -d
16:44:24 Oct  4 1990
[ram:]:

It should have worked fine in 1.4 too, which leads me to wonder
wherther, perhaps you have put this in your .skshrc and not
assigned sksh: do that directory, so SKsh doesn't see the file?
Or perhaps you have a .skshrc.pp file there which is being
executed instead.  Another potential reason is if you execute
(not source) a file which sets HOME, but you don't export
HOME afterwords.  The new variable definition will be lost when
the script exits.

> request:
> I hope they add all the neat variable modifier syntax that KSH has!

By "variable modifier" syntax, do you mean all those ${foo:bar}
style things?  "They" (ie, "I") have been considering adding those,
but no one asked, so I never did...

The best way to get requests implemented is to mail them directly to
me.  It is purely be coincidence that I happen to catch things
about SKsh posted to comp.sys.amiga.*.

  - steve