Maybe I'm dumb and I missed it, but I hadn't seen Lorenzo Colitti's analysis of GNOME startup time mentioned anywhere. Well worth reading.
Filed under misc …
xscope
xscope is so damn useful.
Here's a patch to make it support the SHAPE extension. It'd be really good to get this thing into freedesktop.org and so people can hack on it to make it sane.
I should try out Soeren's gtk xscope wrapper.
I'm not sure what's the best way to build the thing, but if you check it out from keithp's CVS and do:
$> imake -I/cvs/xorg/config/cf
$> make
then it seems to build just fine if you remove the malloc() prototype
in common.c. Of course, if you have a space between the -I and the
path to the xorg build on the imake command line, then you could find
yourself spending a long time trying to figure out wtf is wrong.
Oh, yeah, one final tip. xscope is a proxy Xserver. So, when you connect
your app to xscope, Xlib goes looking in ~/.Xauthority for an xauth
cookie to use when authenticating. Because xscope has a different
display number from the parent display, though, you need to use xauth to
setup the cookie for this display number too. So, assuming the parent
display is :0 and xscope is :1, you can do:
$> xauth list | grep '/unix:0' | while read display proto cookie; do xauth add ${display%0}1 $proto $cookie; done
Marketing Silliness
Caolán and I spent a while being generally childish (like changing the web page on the Sun Rays from sun.com to redhat.com etc.) at the Sun booth at LinuxTag. Much chuckles was had, though, when we saw this:
Marketing people are silly. Vino should clearly have a bigger box than piffling little OpenOffice.org :-)
Xnest Buginess
Anyone that uses Xnest will have gotten annoyed when it gets confused about the modifier state and it thinks e.g. Alt is pressed when its clearly not. Given that the bug has been around forever, it was seriously gratifying to fix it last week.
And before anyone says "Xnest sucks; use Xephr", this is actually a bug in Xephr too ... :-)