Path: utzoo!attcan!uunet!cbmvax!jesup From: jesup@cbmvax.UUCP (Randell Jesup) Newsgroups: comp.sys.amiga Subject: Re: ENV: variables (long) Message-ID: <4781@cbmvax.UUCP> Date: 20 Sep 88 20:14:54 GMT References: <374@uwslh.UUCP> <5660014@hpcvca.HP.COM> <2629@sugar.uu.net> Reply-To: jesup@cbmvax.UUCP (Randell Jesup) Organization: Commodore Technology, West Chester, PA Lines: 23 In article <2629@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes: >In article <5660014@hpcvca.HP.COM>, charles@hpcvca.HP.COM (Charles Brown) writes: >> > FOOBAROPTS, names like FOOBAR.WIDTH, FOOBAR.LINESPERPAGE, FOOBAR.MODE >> > are possible. The command "list-var FOOBAR.*" lists only the FOOBAR >> > variables. > >> This is so sensible that it's frightening. > >It's also possible on the Amiga. > >1> Setenv foobar.width 10 >1> dir env:foobar.#? I'd greatly prefer it if people would use subdirectories (ex: "Setenv foobar/width 10", "dir env:foobar".) I see subdirectories as one of the nice side effects of using a filesystem for env variables (plus getting all those file manipulation programs like copy, rename, dir, etc for free, instead of having to write new ones just for the env variables.) -- Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup