[Coco] Sugestions for new NitrOS-9 versions
boisy at tee-boy.com
Wed Apr 2 12:51:30 EDT 2014
I would suggest following the OS-9/68K model and use environment variables. Even though there aren’t environment variables in NitrOS-9, it might be possible to shoehorn them in.
An area in the process descriptor could be allocated to hold a pointer to a buffer of memory for environment variables. Then F$Fork and F$Chain would consult:
1. the current execution directory
2. all directories in the PATH environment variable
Shellplus does handle multiple execution directories, but this really needs to be outside of the purview of the shell and in the domain of the aforementioned system calls.
On Apr 2, 2014, at 10:50 AM, Luis Antoniosi (CoCoDemus) <retrocanada76 at gmail.com> wrote:
> What would you change on NitrOS-9 for the next versions ?
> I have one suggestion: make the executable path (CHX) multiple and
> relative like:
> chx ./;./cmds;/dd/cmds/
> For example using the path this would make the os-9 search for modules
> first on you current dir, then into a CMDS folder on the same level as
> you are and then finally in the default /dd/cmds
> Why ? because every time you use a second disk you have to type:
> chx /d1/cmds
> and this is very annoying. Then you need to check the DIR if you don't
> have it in your /d1/cmds folder you will need to make
> chx /dd/cmds
> or call:
> What do you think about this suggestion ? Especially using large CF or
> HDDs with apps installed in multiple folders changing CHX everytime is
> a pain. Copying everything to your /dd/cmds is a mess and could cause
> file conflicts.
> Long live the CoCo
> Coco mailing list
> Coco at maltedmedia.com
More information about the Coco