| > [...] There are several reasons as of why certain patches aren't
| > accepted. Some of the patches affect areas of fvwm which in the long
| > term goal should be replaced by modules. Others are unclean, and no
| > one has been willing to clean up the code and write documentation for
| > the patches.
|
| i get this but if no work has happened why cant we use the patches?
| its these delays which make users want to use another window manager
You should be able to use the patches without problems, assuming that
they apply cleanly; just build a personal version of fvwm with the
patches applied. No one requires that you run only fvwm source straight
from the distribution tarballs or the CVS repository.
If the patches do not apply cleanly or do not work as-is, well, someone
has to do the work to make them work. The fvwm maintainers are not going
to do this work for patches that they feel are a bad idea, for obvious
reasons.
- cks, who patches his own version of fvwm and accepts the
job of maintaining those patches
