To you, maybe, to me, no, I want to be able to unmount my home if necessary
and wouldn't want to kill lots of daemons just because I was in the wrong
path when starting them.
OK, I can see your point about processes hanging on to directories
(however it is not relevant to my current or past setups).
If I wanted to annoy you I'd probably ask for a --cwd option to urxvtd.
But rest assured I won't :)
If urxvt::term starts a new terminal window in the same process, please
add that to the documentation. It currently says it acts "very similar
as if you had started it with system()".
Well, it says that because it is true. What's your issue with that? Is it
relevant?
My issue is that "as if you had started it with system()" doesn't make
it clear whether a new process (besides the one executing the Perl code
at that time) is fork()-ed or not. I'm still not sure which way it is.
There is no such thing as "a current terminal" that could be used, and it
doesn't have anything like "a terminal's environment".
$urxvt::TERM and $term->env?
In any case, those arguments are there for a reason. If you want a dumbed
down terminal emulator, you are free to fork.
Making an argument optional (by supplying a default value) dumbs down an
API...?
-- Dan
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
