On Thu, Sep 18, 2008 at 05:33:42PM +0300, Dan Muresan <[EMAIL PROTECTED]> wrote:
> exec_async seems to give executed children an environment with the
> current directory set to /.
That's not the case, exec_async doesn't change the directory.
However, note that the current directory of urxvtd is /, so if you use
urxvtd, then your cwd will always be / (what else should it be, btw.?)
> I wrote the following extension that creates
> a new urxvtc for the current urxvtd (as defined by RXVT_SOCKET).
You can actually simply open a new terminal with something like:
new urxvt::term;
(see the urxvt.pm docuemntation)
> Whenever I use it to create a terminal, that new terminal starts with a
> current dir of /.
Because that *is* the current directory: Terminal windows have no sensible
notion of "current" directory (the window itself has no directory, and
the programs running in them all have their own, possibly different, idea
of cwd), so to get something else you would first have tod efine what
"current directory" should mean.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
