On Fri, Oct 03, 2008 at 06:39:17PM +0200, Rudolf Sykora wrote:
> Hello everybody!
> 
> If I understand it right ^f (or an 'ins' key) are taken care of by rio and
> thus the success of completion is essentially dependent on the namespace rio
> is using. This namespace is created when rio is started, usually right after
> a computer start. When the namespaces of individual windows are changed, e.
> g. by binding some remote filesystems, ^f can't handle those new files
> (since the rio namespace stays intact). Even though I may understand the
> reason (i.e. what I have just said) I find it rather irritating, having
> maybe the whole space I work with out of reach of ^f. Is there any help with
> that? Couldn't it be somehow achieved that ^f worked 'better'? (Not saying
> rc should take care of it, it probably should not; but what about if it were
> somehow connected with the individual windows? -- I don't know, it may not
> be possible, just asking. Having to always write 'lc' is somewhat ...).
> Starting a bunch of several rios can help it. But is that a right way to
> go?
> 
> Thanks for answers.
> Ruda

This was the issue that prompted my experimental work for cross-namespace
visibility (see
https://wiki.ietfng.org/pub/Plan9/KernelInternals/CrossNamespaceWalkProject
if you're curious).  This experiment is probably not the Right Way to do
this, but it may be food for thought.

Another alternative would be to spawn an exportfs "next to" the rc inside
the window, and have rio use that to find completions.  Not terribly
pleasant, but might be workable.

--nwf;