'KillModule' broken

Hello, It seems to me that in current fvwm 2.5.17 CVS branch 'KillModule' command is entirely broken. I built current CVS tree on two different computers with two different GNU/Linux distributions and it don't work. You can easily reproduce this with no config at all: launch any module from

KillModule fix

The attached patch fixes the broken KillModule command. Can someone please apply it? ChangeLog: 2006-07-11 Dominik Vogt dominik(dot)vogt(at)gmx(dot)de * fvwm/module_interface.c (KillModule, ClosePipes): fixed KillModule Ciao Dominik ^_^ ^_^ -- Echte DSL-Flatrate

CVS renato: Applied Dominik's patch to fix broken KillModule

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: renato 06/07/11 04:56:52 Modified files: . : ChangeLog fvwm : module_interface.c Log message: Applied Dominik's patch to fix broken KillModule

CVS griph: ensure that FvwmCommand and FvwmCommandS use the same default names.

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: griph 06/07/11 05:04:51 Modified files: modules: ChangeLog modules/FvwmCommand: FvwmCommand.c FvwmCommand.h FvwmCommandS.c Makefile.am Added files:

using lstat

Is there some define to check for systems that have lstat? /Viktor

Re: KillModule fix

Hi Renato, The attached patch fixes the broken KillModule command. Can someone please apply it? Done. How long was it broken? Not long. Since 2006/06/24. By the way, I've long wanted to know the significance of seventh guardian ... ? SCoTT. :)

Re: KillModule fix

On 7/11/06, Scott Smedley [EMAIL PROTECTED] wrote: Hi Renato, The attached patch fixes the broken KillModule command. Can someone please apply it? Done. How long was it broken? Not long. Since 2006/06/24. Ok, that explains why yesterday I couldn't kill FvwmPager. I didn't give it much

CVS scott: Added Periodic option to Schedule command.

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: scott 06/07/11 09:38:34 Modified files: . : AUTHORS ChangeLog NEWS fvwm : fvwm.1.in schedule.c Log message: Added Periodic option to Schedule command.

CVS griph: fix tempfile vulnerabilities in FvwmCommand (bug #2791).

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: griph 06/07/11 10:16:09 Modified files: . : ChangeLog NEWS configure.ac modules: ChangeLog modules/FvwmCommand: FvwmCommand.1.in FvwmCommand.c

Re: CVS griph: fix tempfile vulnerabilities in FvwmCommand (bug #2791).

On Tue, Jul 11, 2006 at 10:16:09AM -0500, fvwm-workers wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: griph 06/07/11 10:16:09 Modified files: . : ChangeLog NEWS configure.ac modules: ChangeLog modules/FvwmCommand:

Re: using lstat

On Tue, Jul 11, 2006 at 01:36:53PM +0200, Viktor Griph wrote: Is there some define to check for systems that have lstat? Take a look at configure.ac. Just add lstat to one of the AC_CHECK_FUNCS macros and you will get a #define HAVE_LSTAT in the config.h file. Ciao Dominik ^_^ ^_^ --

CVS domivogt: * Fixed parsing of Periodic option.

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt06/07/11 14:38:56 Modified files: . : ChangeLog fvwm : schedule.c Log message: * Fixed parsing of Periodic option.

Re: CVS domivogt: * Fixed parsing of Periodic option.

On Tue, Jul 11, 2006 at 02:38:56PM -0500, fvwm-workers wrote: CVSROOT: /home/cvs/fvwm Module name: fvwm Changes by: domivogt06/07/11 14:38:56 Modified files: . : ChangeLog fvwm : schedule.c Log message: * Fixed parsing of Periodic

FvwmPager: Compilation fix when --enable-debug-msgs is set

Hello, With current state of things it's impossible to compile 2.5.17 CVS branch with --debug-msgs configure option. I investigated created a patch which fixes this problem. Best wishes -- Serge Koksharov, Free Software user supporter GPG public key ID: 0x3D330896 (pgp.mit.edu) Key

CVS renato: Applied Serge's patch correcting --debug-msgs bug.

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: renato 06/07/11 17:44:05 Modified files: modules: ChangeLog modules/FvwmPager: FvwmPager.c Log message: Applied Serge's patch correcting --debug-msgs bug.

Re: FvwmPager: Compilation fix when --enable-debug-msgs is set

On 7/11/06, Serge (gentoosiast) Koksharov [EMAIL PROTECTED] wrote: Hello, With current state of things it's impossible to compile 2.5.17 CVS branch with --debug-msgs configure option. I investigated created a patch which fixes this problem. OOPS that was my fault.. Appiled. BTW, is it my

Re: CVS griph: fix tempfile vulnerabilities in FvwmCommand (bug

On Tue, 11 Jul 2006, Dominik Vogt wrote: On Tue, Jul 11, 2006 at 10:16:09AM -0500, fvwm-workers wrote: CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: griph 06/07/11 10:16:09 Modified files: . : ChangeLog NEWS configure.ac modules:

ChangeLog vs modules/ChangeLog ?

Hi. I have a question regarding the use of the ChangeLogs. Obviously, changes to the fvwm core are reported in the root ChangeLog. But what about changes to modules? I ask this because I've allways logged my changes to the root one, but now think I should have done it to modues/ChangeLog. On

Re: ChangeLog vs modules/ChangeLog ?

seventh guardian [EMAIL PROTECTED] writes: Hi. I have a question regarding the use of the ChangeLogs. Obviously, changes to the fvwm core are reported in the root ChangeLog. But what about changes to modules? I ask this because I've allways logged my changes to the root one, but now think

CVS scott: Comments.

CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: scott 06/07/11 20:22:56 Modified files: . : ChangeLog libs : Parse.c Log message: Comments. Added DV's mailing-list comments about how PeekToken GetNextToken work as comments to the

PeekToken GetNextToken

Hi Dominik, Some hints for using the parsing functions Thanks. I think they are useful, so I added them as comments to the source code. (slightly modified) By the way, I notice that entries in ChangeLog appear not to be in chronological order. I always use the local date - I assume that's ok?