CVS domivogt: * Applied patch for undocumented Pad option in FvwmTaskBar.

2006-04-12 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt06/04/12 15:55:20 Modified files: modules: ChangeLog modules/FvwmTaskBar: FvwmTaskBar.1.in Log message: * Applied patch for undocumented Pad option in FvwmTaskBar.

CVS domivogt: * Applied fvwm-bug safety patch.

2006-04-12 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt06/04/12 15:53:16 Modified files: . : ChangeLog bin: ChangeLog fvwm-bug.in Log message: * Applied fvwm-bug safety patch.

CVS domivogt: * Applied TaskBar namelen patch.

2006-04-12 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt06/04/12 15:58:19 Modified files: . : AUTHORS modules: ChangeLog modules/FvwmTaskBar: FvwmTaskBar.c Goodies.c Start.c Log message: * Applied TaskBar namelen patch.

Re: FVWM: xpad incorrect behaviour under FVWM

2006-04-12 Thread Viktor Griph
On Mon, 10 Apr 2006, Serge (gentoosiast) Koksharov wrote: On Fri, Apr 07, 2006 at 05:55:25PM -0400, Dan Espen wrote: When I turn on edit lock, fvwm interprets the first click (and every click) as a request to move the window. The window-move feedback window appears. Yes, exactly. But in

Re: FVWM: fvwm2 version 2-4-19

2006-04-12 Thread Jonathan Kotta
On 4/12/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dear fvwm supporters, I have downloaded and installed version 2-4-19 of fvwm2 (unzipped, untared, ./configure, make, make install). During compilation, I got numerous error messages stating that files (mostly starting with mini) had

Re: FVWM: xpad incorrect behaviour under FVWM

2006-04-12 Thread Dominik Vogt
On Wed, Apr 12, 2006 at 12:02:08PM +0200, Viktor Griph wrote: On Mon, 10 Apr 2006, Serge (gentoosiast) Koksharov wrote: On Fri, Apr 07, 2006 at 05:55:25PM -0400, Dan Espen wrote: When I turn on edit lock, fvwm interprets the first click (and every click) as a request to move the window. The