For the terminal started directly calling /usr/bin/urxvt, the output is:
WM_CLASS(STRING) = "urxvt", "URxvt"
If I run x-terminal-emulator, I get:
WM_CLASS(STRING) = "x-terminal-emulator", "URxvt"
I'm unsure what to make of this, however.
]]>Use xprop | grep WM_CLASS to check.
]]>Now, I was trying to set this as the default X terminal emulator, using update-alternatives:
# update-alternatives --config x-terminal-emulator
There are 5 choices for the alternative x-terminal-emulator (providing /usr/bin/x-terminal-emulator).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/bin/lxterm 30 auto mode
1 /usr/bin/koi8rxterm 20 manual mode
2 /usr/bin/lxterm 30 manual mode
3 /usr/bin/urxvt 20 manual mode
4 /usr/bin/uxterm 20 manual mode
5 /usr/bin/xterm 20 manual mode
Press enter to keep the current choice[*], or type selection number:
Number 3 seems to be the right choice here, so I selected it and hit enter. But if I use x-terminal-emulator instead of /usr/bin/urxvt now to start the terminal, the configuration (colors, fonts) in my .Xresources file is being ignored and I'm presented with a small white box containing a bit of tiny text in an ugly font and an ugly scroll bar on the left on top of that.
That's pretty strange, because x-terminal-emulator should do nothing but point to /usr/bin/urxvt, which it does. How is it possible then that I get a fully configured RXVT when running /usr/bin/urxvt directly, but not when running x-terminal-emulator?
I'm on Jessie, FWIW.
]]>