Subject: Notification: incoming/996

From: [email-masked]
Date: Fri, 14 Mar 2003 05:37:19 -0600

FVWM Bug Tracking notification

new message incoming/996

Message summary for PR#996
	From: [email-masked]
	Subject: Different usage of display name in fvwm2 and FvwmCommand
	Date: Fri, 14 Mar 2003 05:37:18 -0600
	0 replies 	0 followups

====> ORIGINAL MESSAGE FOLLOWS <====

>From [email-masked] Fri Mar 14 05:37:19 2003
From: [email-masked]
To: [email-masked]
Subject: Different usage of display name in fvwm2 and FvwmCommand
Date: Fri, 14 Mar 2003 05:37:18 -0600

Full_Name: Carsten Prescher
Version: 2.5.5
CVS_Date: 
OS: Linux-2.4.18-14 (RedHat 8.0, 
X_Server: XFree86 4.2.0
Submission from: (NULL) (53.122.197.194)

Precondition: DISPLAY is set to :0

fvwm2 changes the DISPLAY environment variable for all its children to
XDisplayName() which results in DISPLAY=:0.0
Then FvwmCommandS creates the file /var/tmp/FvwmCommand-<hostname>:0.0

If you start FvwmCommand not from a fvwm2-child, the DISPLAY is still :0,
hence FvwmCommand tries to open the file /var/tmp/FvwmCommand-<hostname>:0
and cannot find it.

--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [email-masked].
To report problems, send mail to [email-masked]