Re: [9fans] acme tags for shell scripts

[Russ Cox <russcox@gmail.com>]

> The problem here is that this mechanisms are not uniform.  In rio, /dev/winid is
> the current id of the window.  In an script run in acme this is done
> with $winid.  In win (in acme) the dir is bound in /dev/acme. Wouldn't all this
> have to be the same?.

It's true that they're not uniform.  I'm not sure what you mean by
"have to be the same".  It would definitely be confusing if /dev/winid
gave you acme id's under acme but rio id's under rio.
I agree if you mean that all the context should be in the name
space where it belongs.

The reason acme sets $winid is that I put it in (originally for
the Getdir script, which replaced the builtin Dotfiles) while
I was using the Unix acme, and there I don't have the luxury
of per-process name spaces, but I do have per-process environments.

I'll probably add your bind next time I'm in there.

Russ