From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a560a5d00810030939i7f337a84t5763d3f039ec07b5@mail.gmail.com>
Date: Fri,  3 Oct 2008 18:39:17 +0200
From: "Rudolf Sykora" <rudolf.sykora@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_15013_10234927.1223051957676"
Subject: [9fans] control-F completion question
Topicbox-Message-UUID: 16ab3a2c-ead4-11e9-9d60-3106f5b1d025

------=_Part_15013_10234927.1223051957676
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_15013_10234927.1223051957676
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div dir=3D"ltr">Hello everybody!<br><br>If I understand it right ^f (or an=
 &#39;ins&#39; key) are taken care of by rio and thus the success of comple=
tion 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 re=
mote filesystems, ^f can&#39;t handle those new files (since the rio namesp=
ace stays intact). Even though I may understand the reason (i.e. what I hav=
e just said) I find it rather irritating, having maybe the whole space I wo=
rk with out of reach of ^f. Is there any help with that? Couldn&#39;t it be=
 somehow achieved that ^f worked &#39;better&#39;? (Not saying rc should ta=
ke care of it, it probably should not; but what about if it were somehow co=
nnected with the individual windows? -- I don&#39;t know, it may not be pos=
sible, just asking. Having to always write &#39;lc&#39; is somewhat ...). S=
tarting a bunch of several rios can help it. But is that a right way to go?=
&nbsp; <br>
<br>Thanks for answers.<br>Ruda<br></div>

------=_Part_15013_10234927.1223051957676--