Hello
I encountered sth strange:
being e.g. in my home
; pwd
/usr/ruda
I issue
; @{cd lib}
then lc, pwd seems to be ok, lists/returns my home directory, but the
completion with ctrl-f/ins proposes things from the 'lib' directory.
What's going on? I really can't live without the completion func
> I issue
> ; @{cd lib}
>
> then lc, pwd seems to be ok, lists/returns my home directory,
This makes sense to me - though I am not saying its "correct".
When you cd in interactive mode rc(1) writes the path to the
directory into /dev/wdir. This informs rio of your current dir
so it can do the fi
Rudolf Sykora wrote:
> I really can't live without the completion function...
how come? I've *never* used it
> I remember reading some discussion in OpenBSD/NetBSD. I was wondering
> if someone already tried netbsd/9vx?
There was some work done for OpenBSD. I tried compiling it
under NetBSD and didn't find happiness. I don't remember now
what the issue was, and I haven't had time to go back an
look mor
> > This guy seems to blur the distinctions here. His discussion
>
> He doesn't. If one reads the whole section part of which was quoted one
> will see that he clearly states DFA and NFA are theoretically equivalent,
> but then goes on to explain that DFA and NFA _implementations_ are not
> id
It is merely the traditional POSIX flavor. Some people like that
flavor, some don't.
Understandable.
It is more that Perl simply was never part of the picture for the people
who develop(ed) and use(d) Plan 9. It's like asking why the paper on
the Plan 9 C compiler doesn't state that C++ clas
2008/10/28 matt <[EMAIL PROTECTED]>:
> Rudolf Sykora wrote:
>>
>> > I really can't live without the completion function...
>
> how come? I've *never* used it
... this is hard to comment on...
Ruda
Thanks for the explanations. The lowlife learns a bit or two :-)
--On Tuesday, October 28, 2008 2:51 PM + "Brian L. Stuart"
<[EMAIL PROTECTED]> wrote:
> This guy seems to blur the distinctions here. His discussion
He doesn't. If one reads the whole section part of which was quoted one
w
> When you cd in interactive mode rc(1) writes the path to the
> directory into /dev/wdir. This informs rio of your current dir
> so it can do the filename completion (and also gives the directory
> context to the plumber).
>
> I guess the @{ } "execute in a subshell" code in rc could save and rest
cd .
is sufficient
-rob
> cd .
>
> is sufficient
>
> -rob
As I wrote in my initial mail, 'cd .' does not help.
Ruda
the bug is within rio, which keeps track of changed directories but
doesn't know that some of them are changed on a stack for a child
process. the actual code is in xfid.c:^xfidwrite, the Qwdir case. what
is happening is that it catches the 'cd /lib' correctly and sets
w->dir accordingly, however t
> As I wrote in my initial mail, 'cd .' does not help.
pwd >/dev/wdir
cd . works for fixing acme's tag (if your cd runs awd)
but not for fixing /dev/wdir, because rc just writes the
argument to cd uninterpreted into /dev/wdir, and
/dev/wdir interprets paths relative to the current wdir setting.
> - use getpw() instead of w->dir for unrooted arguments to cd (the
> return value of getpw() is correct after the subshell command
> completes)
scratch that, it is incorrect. i only tried getpw() from the shell.
rio doesn't necessarily live in the same world as the shells in its
windows.
thanks
This saving&restoring seems flawed to me due to possible race-conditions...
I'd expect each shell had its own copy of /dev/wdir... But I may be
easily wrong...
When a rc forks a subshell the child shares the namespace with the parent.
If you want the child rc to divorce its namespace from the p
> When a rc forks a subshell the child shares the namespace with the parent.
> If you want the child rc to divorce its namespace from the parent, have it
> issue 'rfork n'.
This is true, but I am afraid it doesn't have much connection to the problem.
Even if you 'rfork n' (and have a copy of the n
This is true, but I am afraid it doesn't have much connection to the problem.
Even if you 'rfork n' (and have a copy of the namespace) the file
/dev/wdir is simply the same file in both namespaces...
Yes, I realized after I hit send that I wasn't very clear about what I was
trying to say. I was
17 matches
Mail list logo
