23 Apr
2010
23 Apr
'10
3:25 p.m.
Louis Zulli <zullil@lafayette.edu> writes:
On Apr 23, 2010, at 11:02 AM, robert delius royar wrote:
Also, another poster mentioned that on his system, his display includes the directory.
No problem on either my MacBook or my MacPro, both running 10.6.3 and XQuartz 2.5.1_beta2 (xorg-server 1.8.0) LZsMacPro-OSX6: ~] echo $DISPLAY /tmp/launch-wdWo9a/org.macosforge.xquartz:0
I just ran into this same problem (and filed ticket #390 about it). Now that I re-read this thread, I notice that on 2.5.0 I have $ echo $DISPLAY /tmp/launch-Cz75dW/org.macosforge.xquartz:0 whereas in beta2 I was seeing just "org.macosforge.xquartz:0.0". So that's the source of the problem, but what could be mis-setting the environment variable? regards, tom lane