CVS dane: * FAQ (6.8): Fix text to use same number of buttons as subject line.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: dane04/09/01 08:12:48 Modified files: docs : ChangeLog FAQ Log message: * FAQ (6.8): Fix text to use same number of buttons as subject line. -- 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]
CVS domivogt: * Elaborate on number of usable mouse buttons in the man page.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt04/09/01 08:44:54 Modified files: . : NEWS fvwm : fvwm.1.in Log message: * Elaborate on number of usable mouse buttons in the man page. -- 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]
CVS domivogt: * Numerous fixes and changes in support for 5 mouse buttons.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt04/09/01 09:55:19 Modified files: . : ChangeLog docs : FAQ fvwm : add_window.c bindings.c borders.c builtins.c decorations.c events.c focus.c focus_policy.h frame.c frame.h fvwm.1.in fvwm.c fvwm.h move_resize.c screen.h style.c libs : Bindings.c defaults.h modules: ChangeLog modules/FvwmButtons: FvwmButtons.c modules/FvwmIconBox: FvwmIconBox.c modules/FvwmIconMan: readconfig.c x.c modules/FvwmProxy: FvwmProxy.c modules/FvwmTaskBar: FvwmTaskBar.c Start.c Start.h modules/FvwmWinList: FvwmWinList.c Log message: * Numerous fixes and changes in support for 5 mouse buttons. -- 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]
CVS domivogt: * Corrected formatting.
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt04/09/01 10:00:11 Modified files: docs : FAQ Log message: * Corrected formatting. -- 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]
m4 Macros for configure
Hi. The definition of smr_SWITCH (in both acinclude.m4 and aclocal.m4) uses m4_substr and m4_len, neither of which exist in any m4 I know about. (The three on my Solaris 8 machine are /usr/ccs/bin/m4, /usr/xpg4/bin/m4, and GNU m4 1.4.) Does this exist in some newer or more odd M4? Shouldn't we just use substr and len? The sign that this has failed is in the --help output of the generated configure. It contains the macro calls, rather than the intended strings resulting from the macro. Anyone know where these came from? (And why there's ones in both aclocal.m4, and acinclude.m4?) - Chris -- 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]
Re: m4 Macros for configure
On 01 Sep 2004 11:36:02 -0400, Chris Ross wrote: Hi. The definition of smr_SWITCH (in both acinclude.m4 and aclocal.m4) uses m4_substr and m4_len, neither of which exist in any m4 I know about. (The three on my Solaris 8 machine are /usr/ccs/bin/m4, /usr/xpg4/bin/m4, and GNU m4 1.4.) Does this exist in some newer or more odd M4? Shouldn't we just use substr and len? The sign that this has failed is in the --help output of the generated configure. It contains the macro calls, rather than the intended strings resulting from the macro. Anyone know where these came from? (And why there's ones in both aclocal.m4, and acinclude.m4?) You need a more recent autoconf. This part is tricky, I know how to make autoconf = 2.13 happy and autoconf 2.13 happy, but not both together. If someone knows, feel free to fix this, but I don't think it worth the effort. It only affects the --help output, and if the recent autoconf is used to create releases, then the release will be ok. Regards, Mikhael. -- 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]
Re: m4 Macros for configure
Mikhael Goikhman wrote: You need a more recent autoconf. This part is tricky, I know how to make autoconf = 2.13 happy and autoconf 2.13 happy, but not both together. If someone knows, feel free to fix this, but I don't think it worth the effort. It only affects the --help output, and if the recent autoconf is used to create releases, then the release will be ok. Well, at the very least, you could check which version of autoconf is running, right? And if it's = 2.13, you can redefine m4_substr and m4_len to substr and len, yes? I'll take a look into autoconf and see if I see how to do this anywhere from inside of m4... - Chris -- 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]
Re: m4 Macros for configure
On 01 Sep 2004 11:36:02 -0400, Chris Ross wrote: Anyone know where these came from? (And why there's ones in both aclocal.m4, and acinclude.m4?) aclocal.m4 is generated from acinclude.m4 by aclocal that's from automake (before this generated file is used by autoconf to generate ./configure). Regards, Mikhael. -- 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]
Re: m4 Macros for configure
Mikhael Goikhman wrote: aclocal.m4 is generated from acinclude.m4 by aclocal that's from automake (before this generated file is used by autoconf to generate ./configure). Excellent. Thank you for that information. Okay, I've applied a fairly ugly patch to acinclude.m4. It tears apart the AC_ACVERSION macro into the major and minor number [string]s, and then if the minor number is 13, defines m4_substr and m4_len. It works for me, and I've tested that the macro leaves m4_* unset when I hand-feed it a 2.51 instead of AC_ACVERSION. Unfortunately, m4 only knows about strings. So, do do a = 2.13, I'd have to use syscmd() and sysval(). I could do that, but I wasn't sure it was worth the effort. But, I don't know what versions of autoconf are likely to be in use. Let me know if anything like this would be acceptable. Thanks... - Chris Index: acinclude.m4 === RCS file: /home/cvs/fvwm/fvwm/acinclude.m4,v retrieving revision 1.49 diff -u -u -r1.49 acinclude.m4 --- acinclude.m48 Jul 2004 10:08:09 - 1.49 +++ acinclude.m41 Sep 2004 17:50:11 - @@ -103,6 +103,17 @@ fi ]) +dnl Versions of autoconf 2.13 and older don't have m4_substr and m4_len +dnl built into them. So, check the version of autoconf we're running, +dnl and if it's 2.13, substitude alternative definitions for them. +define([SEGMENT1],[substr([$1],0,ifelse(index([$1],.),-1,len([$1]),index([$1],.)))])dnl +define([SEGMENT2],[ifelse( index([$1],.), -1, [], SEGMENT1(substr([$1], incr(index([$1],.)])dnl + +define([AC_ACVERSION_MAJOR],[SEGMENT1(AC_ACVERSION)])dnl +define([AC_ACVERSION_MINOR],[SEGMENT2(AC_ACVERSION)])dnl +ifelse(AC_ACVERSION_MINOR,13, +[define([m4_substr],[substr([$1],[$2])])dnl +define([m4_len],[len([$1])])dnl])dnl dnl Configure-time switch with default dnl
