Marc Lehmann 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.?)
By a terminal's "current directory", I mean the current dir for the
shell embedded in that terminal (as shown by both the bash prompt and
the pwd command).
Let me rephrase my original report: in urxvt terminal A, the "current
dir" is /home/muresan.
I run "urxvtd &" in terminal A. I then run urxvtc (also in terminal A)
which fires up urxvtc terminal B.
In B, both the prompt and pwd confirm that the current dir is still
/home/muresan.
Now I activate the extension described in my last e-mail (by bringing up
the options popup for terminal B and selecting menu item URxvtC).
Terminal C opens. In terminal C, both the prompt and pwd show that the
current dir is /. The current dirs in A and B remain /home/muresan.
What causes C to get a current dir of /, instead of /home/muresan like
B? I thought exec_async might be to blame, but you're saying that's not it.
new urxvt::term;
Would that re-use the urxvtd associated with the current terminal?
Because that was the purpose of the extension (bring up a new urxvtc
associated with the same urxvtd as the current terminal).
(see the urxvt.pm docuemntation)
I've seen it, didn't think it would do what I described above :)
Thanks,
Dan
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
