On 2009 Dec 26, Thomas Adam wrote:
> Is there anyone on the list who wouldn't mind checking out the FVWM CVS
> repository and giving the fvwm-convert-2.6 script a go? It has a manpage as
> well which describes what the script will try and do -- on the limited
> amount of testing I've done with con
On 2009 Dec 31, Thomas Adam wrote:
> On Tue, Nov 03, 2009 at 10:57:00PM -0800, Derek B. Noonburg wrote:
>> There is some code at the end of HandleClientMessage() that forwards
>> ClientMessage events on to the client window. It's marked with a
>> comments that says "I'm not so sure this should be
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: tadam 10/01/04 06:00:38
Modified files:
. : ChangeLog
fvwm : events.c
Log message:
Add missing XAtom type to struct when flushing property events.
Make sure we propagate the actual atom
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: tadam 10/01/04 05:53:34
Modified files:
. : ChangeLog NEWS
fvwm : events.c events.h
Log message:
Apply property event handling patch (D. Fries)
Modified version of original patch to cor
On Sat, Mar 21, 2009 at 06:27:39PM -0500, David Fries wrote:
> This version includes a ChangeLog entry. I found this performance
> problem from GnuCash updating the title and icon for each window for
> each transaction when doing a check and repair.
Good analysis, thanks. Saw this recently in Op
On Sun, Mar 01, 2009 at 04:08:57PM -0600, David Fries wrote:
> history and bug report:
> I just upgraded fvwm and saw an edge bump behavior at the outside
> paging border when moving a window. When a window was moved into the
> panning window the poiner and window would be bumped so the pointer
>
CVSROOT:/home/cvs/fvwm
Module name:fvwm
Changes by: tadam 10/01/04 04:14:53
Modified files:
. : ChangeLog NEWS
fvwm : move_resize.c virtual.c
Log message:
Apply window-jump fix (D. Fries).
Applied window-jump fix when moving windows acro
On Sun, Jan 03, 2010 at 10:27:31PM -0600, David Fries wrote:
> Here's a patch to help people bootstrap from CVS, autoheader trips me
> up everytime. It doesn't have to go in INSTALL.fvwm, it could be
> INSTALL (or as I've seen others a `bootstrap.sh' ) but if it's
> available someplace it would be
