[Fink-users] XCode 3.1 & XQuartz 2.3.0 experience report?

[Richard C. <co...@cc...>]

Thus far, I've resisted upgrading to XCode 3.1 and XQuartz 2.3.0; I'm
currently running XCode 3.0 and XQuartz 2.2.1 on 10.5.4/intel.  However, it
looks like I'm going to have to, as I just encountered the problem in the
ongoing thread "Failed: phase compiling: libtheora0-1.0-1.beta3.1 failed",
which seems to require upgrading XCode, which in turn requires upgrading
XQuartz.

I've thus far avoided the upgrade because I've had bad experiences with
XQuartz 2.3.0.  I realize that this isn't necessarily the best forum for
this, and I'll check on Apple's X11 mailing list, but I'd like to know if
anyone else has seen this behavior and especially if anyone has a
workaround.

I've seen two problems with XQuartz 2.3.0.  The first and much less severe
of the two is that XQuartz appears to ignore the OS X "input source"
setting.  If, for instance, I have the current input source set to, say,
Greek, and I type into an XTerm, I get the same results as when the input
source is set to U.S., the machine's default (and the input source that was
selected when X started).  Works fine in other apps, like TextEdit, and in
XQuartz 2.2.1.  (I'm running uxterm, so it's unicode-aware; I'm pretty sure
that's not the problem.)

A much bigger problem is poor interaction with Spaces.  This manifested
itself in a particularly annoying way as follows.  I've got 4 spaces set up
in a 2x2 grid; X11 clients are configured to appear on space 1, and
Emacs.app is configured to appear on space 3.  I use fink's mutt, running
in a uxterm (on space 1) as my primary mail client, and it's configured to
use emacsclient as its editor.  So, the normal workflow: hit "m" in mutt to
compose an email, enter addressee and subject, then switch (via kbd) to
space 3 to compose the message.  Hit C-x # to save the message and return
control to mutt, then kbd-switch back to space 1 to finish up, attach any
attachments, and send the message.

Under 2.2.1, works fine.  Under 2.3.0, the act of switching between spaces
1 and 3 seems to put some keystrokes in the uxterm's input channel (or
whatever the correct term is), which mutt then tries to interpret as
commands.  Under certain circumstances, these keystrokes would send the
message before I had attached a necessary file.  I went through about 3
iterations of this (to the same person, with successive messages saying,
"sorry, mailer client fubar'd, this time attached"; "no, really, this
time!"; "oh, forget it; it's on my web page") before I finally gave up and
downgraded.

Has anybody seen this?  Any thoughts on workarounds?

Thanks,

Richard