most /env things haven't got newlines so wc -l /env/* generally gives 0. you also need to watch the binding in things like this:
2012/5/16 <[email protected]> > @{rfork e; echo hi} >/env/hi ie, the env file might be created in the parent name space, because the > is done before the @, and in the scope above the rfork e, compared to term% @{rfork e; echo hi >/env/hi} term% ls /env/hi ls: /env/hi: '/env/hi' file does not exist
