> written. I would like to get other folks' evaluations > of the work so it can be improved.
just a couple minor details: 1) in http://dlc.casita.net/~dlc/vp9cb/tc05.png, you do not need such kernel messages scribbling on top of rio. just swipe another window off an edge run cat /dev/kprint. /dev/kmesg holds past kernel messages and /dev/kprint will show them as they come. 2) 'what's up with the world-writable attribute?' it does not really matter. if some other process writes to that variable, it is modified in the namespace of that other process. none of the others are affected. also, for functions, you can just use 'fn funcname' to undefine it. removing a variable from /env does not undefine it, but you can clear its contents with var=''. a script will leave its variables in /env too (albeit with empty values), so if you do not want that, put an 'rfork e' at the top. this creates a copy of the current environment, but any changes happen only in the copy which disappears when the script is done. 3) if you want a default rio environment similar to that of glenda for your user account when using drawterm or booting back up as a terminal, you can do the following: % cp /usr/glenda/bin/rc/^(screensize riostart) $home/bin/rc and then change the rio command line in your lib/profile to 'rio -i riostart' to get a few toys to play with. riostart is just an rc script, so you can edit to taste.
