If I wanted to annoy you I'd probably ask for a --cwd option to urxvtd.
But rest assured I won't :)
It's pointless - you can just chdir in your code for the same effect.
Except that with a --cwd option there would be no need for code at all,
I could just add that to .fluxbox/menu. Ever put yourself in a user's shoes?
Anyway, I didn't start coding urxvt extensions because it's fun. I did
it because urxvt is missing some very basic necessities (e.g. the xterm
font menu). Yeah, I know, it's open source and all that load, don't even
remind me.
Nice out of context quoting - the documentation says "similar to", not "as
if you had started it with system".
Didn't mean to, but I don't see how that makes a difference.
In either case, it's not relevant where the terminal is being opened as
long as the API stays as documented, right?
I'm not sure what you mean; the API documentation seems uneven (some
parts are very well documented, others have holes).
The urxvt reference is not a programming tutorial, you need to learn
common sense programming elsewhere, this does not belong in a reference
manual.
I'm fairly sure I'm not missing any basic qualities, and I'm fairly sure
the documentation is obscure on the fork() question :) But it's your
call, again.
$urxvt::TERM and $term->env?
If you think that as "current environment", why is it so hard to use it?
I found it after digging for a while. I wish I didn't have to dig. But I
guess that, just like people, some pieces of software are friendly and
others are not.
-- Dan
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
