FVWM Bug Tracking notification
new message incoming/828
Message summary for PR#828
From: [EMAIL PROTECTED]
Subject: Fvwm-to-Module Communication probably isn't up to date
Date: Fri, 14 Dec 2001 15:17:11 -0600
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Fri Dec 14 15:17:12 2001
Received: from karazm.math.uh.edu ([129.7.128.1])
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 16Ezhf-0000Td-00
for [EMAIL PROTECTED]; Fri, 14 Dec 2001 15:17:12 -0600
Received: from malifon.math.uh.edu (IDENT:[EMAIL PROTECTED] [129.7.128.13])
by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id PAA20093
for <[EMAIL PROTECTED]>; Fri, 14 Dec 2001 15:17:11 -0600 (CST)
From: [EMAIL PROTECTED]
Received: from localhost ([127.0.0.1] ident=65534)
by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
id 16Ezhf-0000TZ-00
for [EMAIL PROTECTED]; Fri, 14 Dec 2001 15:17:11 -0600
To: [EMAIL PROTECTED]
Subject: Fvwm-to-Module Communication probably isn't up to date
Message-Id: <[EMAIL PROTECTED]>
Date: Fri, 14 Dec 2001 15:17:11 -0600
Full_Name: Eugene Morozov
Version: 2.4.0
CVS_Date:
OS: Debian testing/unstable
X_Server: XFree86 4.1.0
Submission from: (NULL) (195.190.97.106)
I'm updating fvwmpy module (it allows to write Fvwm modules in Python) and
it seems that recent changes to Fvwm-to-Module interface aren't reflected
in the documentation. It doesn't say, for example, what's the difference
between M_OLD_ADD_WINDOW and M_ADD_WINDOW. Without such information it is
extremely hard to fix the module. Please, let me know where to find
information about recent changes in the module interface or put updated
documentation on the web site. I just can't force myself to write modules
in C.
--
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 PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
