[fvwmorg/fvwm] 1a05b1: NEWS

2016-12-28 Thread Thomas Adam
  Branch: refs/heads/master
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 1a05b19174c2aaab4da6e21f8243f23ca79af8c4
  
https://github.com/fvwmorg/fvwm/commit/1a05b19174c2aaab4da6e21f8243f23ca79af8c4
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS




[fvwmorg/fvwm] 1a05b1: NEWS

2016-12-28 Thread Thomas Adam
  Branch: refs/heads/ta/module-mdoc
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 1a05b19174c2aaab4da6e21f8243f23ca79af8c4
  
https://github.com/fvwmorg/fvwm/commit/1a05b19174c2aaab4da6e21f8243f23ca79af8c4
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS




Re: Manpage patch + NEWS patch for 2.6.7

2016-12-28 Thread Thomas Adam
On Wed, Dec 28, 2016 at 02:09:25PM -0700, Jaimos Skriletz wrote:
> Additionally it was also pointed out that FvwmDebug was not included
> in the list of removed modules in the NEWS file.

No point patching NEWS since it's in the release tarball anyway.

No one is going to miss FvwmDebug, and the NEWS file is never an entire record
of changes, just the more salient ones.  In other words, I wouldn't rely on it
listing everything.  For that, we have the git history.  The entire thing is
one huge appeasement for GNU.

-- Thomas Adam



[fvwmorg/fvwm] 027774: Remove references to old modules

2016-12-28 Thread Thomas Adam
  Branch: refs/heads/ta/module-mdoc
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 027774b2a39fb7d9d53e3528b9a3b974c098c643
  
https://github.com/fvwmorg/fvwm/commit/027774b2a39fb7d9d53e3528b9a3b974c098c643
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M doc/commands/Asterisk.xml
M doc/commands/Colorset.xml
M doc/commands/DestroyModuleConfig.xml
M doc/commands/LocalePath.xml
M doc/commands/Module.xml
M doc/commands/Style.xml
M doc/commands/Wait.xml
M doc/fvwm/colorsets.xml
M doc/fvwm/initialization.xml
M doc/fvwm/virtualDesktop.xml
M modules/FvwmBacker/FvwmBacker.1.in
M modules/FvwmButtons/FvwmButtons.1.in
M modules/FvwmForm/FvwmForm.1.in
M modules/FvwmIconMan/FvwmIconMan.1.in
M modules/FvwmIdent/FvwmIdent.1.in
M modules/FvwmPager/FvwmPager.1.in
M modules/FvwmScript/FvwmScript.1.in

  Log Message:
  ---
  Remove references to old modules




[fvwmorg/fvwm] 0aac9b: Remove references to old modules

2016-12-28 Thread Thomas Adam
  Branch: refs/heads/ta/module-mdoc
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 0aac9bd80cfd05b6dbc5256f471edabcc9393fe7
  
https://github.com/fvwmorg/fvwm/commit/0aac9bd80cfd05b6dbc5256f471edabcc9393fe7
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M doc/commands/Asterisk.xml
M doc/commands/Colorset.xml
M doc/commands/DestroyModuleConfig.xml
M doc/commands/LocalePath.xml
M doc/commands/Module.xml
M doc/commands/Style.xml
M doc/commands/Wait.xml
M doc/fvwm/colorsets.xml
M doc/fvwm/initialization.xml
M doc/fvwm/virtualDesktop.xml
M modules/FvwmBacker/FvwmBacker.1.in
M modules/FvwmButtons/FvwmButtons.1.in
M modules/FvwmForm/FvwmForm.1.in
M modules/FvwmIconMan/FvwmIconMan.1.in
M modules/FvwmIdent/FvwmIdent.1.in
M modules/FvwmPager/FvwmPager.1.in
M modules/FvwmScript/FvwmScript.1.in

  Log Message:
  ---
  Remove references to old modules




Manpage patch + NEWS patch for 2.6.7

2016-12-28 Thread Jaimos Skriletz
Hello,

A Debian user pointed out that the manpages still mentioned some of
the removed modules. The attach patch either removes or updates the
manpages reference to the modules that were removed in 2.6.7.

Additionally it was also pointed out that FvwmDebug was not included
in the list of removed modules in the NEWS file.

Attached are patches to use as needed.

jaimos
--- a/doc/commands/Module.xml
+++ b/doc/commands/Module.xml
@@ -26,7 +26,6 @@ spawned. Currently several modules, incl
 ,
 ,
 ,
-,
 ,
 
 support aliases.  Aliases are useful if more than one instance of
@@ -53,12 +52,8 @@ Module FvwmForm MyForm
  (a command server to use with shell's FvwmCommand client),
  (to execute fvwm commands directly),
  (to preprocess your config with cpp),
- (to help debug fvwm),
- (the place to dragdrop to),
  (trigger various actions by events),
  (to bring up dialogs),
- (to bring up GTK menus and dialogs),
- (like the mwm IconBox),
  (a flexible icon manager),
  (to get window info),
  (to preprocess your config with m4),
@@ -66,16 +61,7 @@ Module FvwmForm MyForm
  (a Perl manipulator and preprocessor),
  (to locate and control obscured windows by using small proxy windows),
  (to rearrange windows),
- (saves the desktop state in .xinitrc style),
- (saves the desktop state in fvwm commands),
  (another powerful dialog toolkit),
- (puts scrollbars on any window),
- (a generic tabbing module),
- (a Windows like task bar),
- (managed colorsets, obsolete),
- (an AfterStep like button bar),
- (a configurable fvwm menu listing current windows),
- (a window list).
 These modules have their own man
 pages.  There may be other modules out on there as well.
 
--- a/doc/commands/Colorset.xml
+++ b/doc/commands/Colorset.xml
@@ -237,22 +237,15 @@ uses Colorset 10 as background. If you w
 the
 RootTransparent
 option.
-,
+
 ,
-,
-
 and
-
+,
 are relatively simple. There is one main colorset option which
 defines the background of the window and the other colorsets (if
 any) are drawn on the foreground. The case of
- and
-
-are simpler. With
-
-all the colorsets are drawn on the foreground and with
 
-the two colorsets refer to the window backgrounds.
+is simpler, the two colorsets refer to the window backgrounds.
 
 is more complicated as almost everything in the pager are windows
 with some parental relations (the mini windows are the child and
--- a/doc/fvwm/initialization.xml
+++ b/doc/fvwm/initialization.xml
@@ -136,14 +136,14 @@ is used instead of ExitFunction.
  InitFunction
  InitFunction
  + I  
- + I  
+ + I  
  + I  xsetroot -solid cyan
  + I  xterm
  + I  netscape
 
  RestartFunction
  RestartFunction
- + I  
+ + I  
 
  SessionInitFunction
  SessionInitFunction
--- a/doc/commands/LocalePath.xml
+++ b/doc/commands/LocalePath.xml
@@ -87,8 +87,6 @@ parameter:
 available.
 
 Note that the
-
-module has its own catalog and that the
 
 module has a set of special instructions for string
 translation. It is out of the scope of this discussion to explain
--- a/doc/commands/Style.xml
+++ b/doc/commands/Style.xml
@@ -1105,7 +1105,7 @@ window. This miniature icon can be drawn
 (see
 ),
 and can be used by various fvwm modules
-(,  and ).
+( and ).
 It takes the name of a pixmap as an argument.
 
  and 
@@ -2265,8 +2265,8 @@ Style rxvt !State 11
 
 styles do not appear in the menu that is created with the
 
-command or the lists shown in several modules like
- or .
+command or the lists shown in modules like
+.
 In the modules, the style can usually be ignored with an option.
 Please refer to the man page of the module in question for
 further information.  To disable this feature, use the default
--- a/doc/commands/Wait.xml
+++ b/doc/commands/Wait.xml
@@ -44,8 +44,8 @@ After the xmh window appears control mov
 Fvwm remains partially functional during a wait, but any input
 from the modules is queued up and processed only after the window
 appears or the command is aborted.  For example, windows can not
-be focused with  or 
- during a wait.
+be focused with  or
+ during a wait.
 
 You can escape from a
 Wait
--- a/doc/fvwm/colorsets.xml
+++ b/doc/fvwm/colorsets.xml
@@ -24,7 +24,8 @@ other color operations.
 
 was introduced to manage colorsets.  Starting with the 2.5.x beta
 version, the  functionality was moved to the core fvwm,
-so this module became obsolete.
+so this module became obsolete. In 2.6.7 the 
+module was removed.
 
 The old syntax:
 
--- a/doc/fvwm/virtualDesktop.xml
+++ b/doc/fvwm/virtualDesktop.xml
@@ -29,11 +29,11 @@ windows on a range of desktops can be vi
 ,
 a miniature view of the desktops.  The pager is an accessory
 program, called a module, which is not essential for the window
-manager to operate.  Windows may also be listed, along with their
-geometries, in a window list, accessible as a pop-up menu, or as a
-separate window, called the
-
-(another module).
+manager to operate.  Windows may also be listed using the
+
+command or the
+
+module.
 
 Fvwm keeps the windows on the desktop in a 

[fvwmorg/fvwm]

2016-12-28 Thread domivogt
  Branch: refs/heads/dv/pending-patches
  Home:   https://github.com/fvwmorg/fvwm


[fvwmorg/fvwm]

2016-12-28 Thread domivogt
  Branch: refs/heads/dv/fix-disappering-windows
  Home:   https://github.com/fvwmorg/fvwm


[fvwmorg/fvwm]

2016-12-28 Thread domivogt
  Branch: refs/heads/dv/stable-fvwm2
  Home:   https://github.com/fvwmorg/fvwm


[fvwmorg/fvwm] b2f4bc: !!! Start work on replacing the parsing in __execu...

2016-12-28 Thread Dominik Vogt
  Branch: refs/heads/dv/new-parser-2
  Home:   https://github.com/fvwmorg/fvwm
  Commit: b2f4bce686118c71e3b2c22c2905479588af303f
  
https://github.com/fvwmorg/fvwm/commit/b2f4bce686118c71e3b2c22c2905479588af303f
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/Makefile.am
M fvwm/add_window.c
M fvwm/builtins.c
A fvwm/cmdparser.h
A fvwm/cmdparser_old.c
A fvwm/cmdparser_old.h
M fvwm/colorset.c
M fvwm/conditional.c
M fvwm/events.c
M fvwm/ewmh.c
M fvwm/ewmh_events.c
M fvwm/expand.c
M fvwm/expand.h
M fvwm/functions.c
M fvwm/functions.h
M fvwm/fvwm.c
M fvwm/fvwm.h
M fvwm/menucmd.c
M fvwm/menus.c
M fvwm/module_interface.c
M fvwm/move_resize.c
M fvwm/read.c
M fvwm/repeat.c
M fvwm/schedule.c
M fvwm/update.c
M fvwm/virtual.c
M fvwm/windowlist.c

  Log Message:
  ---
  !!! Start work on replacing the parsing in __execute_command_line ...

... with hook functions that are implemented elsewhere.  This aims
at allowing to writing and testing multiple parsers in parallel
and at moving all parsing and expansion stuff to a different
place.


  Commit: e4ee0c738b5df1504d6a8736e3ebf93f86a3a28c
  
https://github.com/fvwmorg/fvwm/commit/e4ee0c738b5df1504d6a8736e3ebf93f86a3a28c
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/cmdparser.h
M fvwm/cmdparser_old.c
M fvwm/functions.c

  Log Message:
  ---
  add debug output and fix positional arguments


  Commit: a8d1bf48531d00c10dc17ed3ba95905ca0b4748e
  
https://github.com/fvwmorg/fvwm/commit/a8d1bf48531d00c10dc17ed3ba95905ca0b4748e
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/cmdparser_old.c
M fvwm/functions.c

  Log Message:
  ---
  add debug output and fix command line prefixes


  Commit: a7a34304f8bb06013b4189f67da44092f1795ec5
  
https://github.com/fvwmorg/fvwm/commit/a7a34304f8bb06013b4189f67da44092f1795ec5
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/Makefile.am
M fvwm/cmdparser.h
A fvwm/cmdparser_hooks.h
M fvwm/cmdparser_old.c
M fvwm/conditional.h
M fvwm/functable.c
M fvwm/functable.h
A fvwm/functable_complex.c
A fvwm/functable_complex.h
M fvwm/functions.c
M fvwm/functions.h
M fvwm/fvwm.h
M fvwm/misc.c
M fvwm/repeat.c
M fvwm/screen.h
M libs/FScreen.h

  Log Message:
  ---
  Convert special logic in __execute_command_line for functions ...

... that may move a window to a separate function flag.

Move find_builtin_function() to functable.[ch].

Moved some functions to functable.[ch] and functable_complex.[ch].

This separation is needed for the parsing hooks.  It was very difficult to get
the #icludes right.  The DesktopsInfo structure was moved to libs/FScreen.h
so that the library does not depend on core header files anymore.

Move WindowConditionMask from mvwm.h to conditional.h.

Finish 1st draft of hook implementation (__execute_command_line)


  Commit: 18e740675182d319189d298f2d27abd53b15b15c
  
https://github.com/fvwmorg/fvwm/commit/18e740675182d319189d298f2d27abd53b15b15c
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/cmdparser.h
M fvwm/cmdparser_hooks.h
M fvwm/cmdparser_old.c
M fvwm/expand.c
M fvwm/functions.c

  Log Message:
  ---
  Split pos_args into a string with all positional args and an array.


  Commit: ce22e8d80c29240799f75aa3f1e659cffbfbbde6
  
https://github.com/fvwmorg/fvwm/commit/ce22e8d80c29240799f75aa3f1e659cffbfbbde6
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/builtins.c
M fvwm/events.c

  Log Message:
  ---
  Update execute_function calls for libstroke.


  Commit: 4149c9a1234627cc0a40ee696e86e5fe364a2c80
  
https://github.com/fvwmorg/fvwm/commit/4149c9a1234627cc0a40ee696e86e5fe364a2c80
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/cmdparser_old.c
M fvwm/functions.c
M fvwm/modconf.c
M modules/FvwmButtons/dynamic.c

  Log Message:
  ---
  !!!debug fprintfs


  Commit: 82672e0e905aca13b9a2615215488a2a549255d9
  
https://github.com/fvwmorg/fvwm/commit/82672e0e905aca13b9a2615215488a2a549255d9
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M libs/FScreen.h

  Log Message:
  ---
  Reinstate libs/FScreen.h


  Commit: ab97d146234acf939f520cff4ed0569cf8a24ecc
  
https://github.com/fvwmorg/fvwm/commit/ab97d146234acf939f520cff4ed0569cf8a24ecc
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed 

[fvwmorg/fvwm] 7cfd20: Improve and clean up size hints warnings.

2016-12-28 Thread Dominik Vogt
  Branch: refs/heads/master
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 7cfd209e17ed88c34f7ec9318dd82aabc3757baa
  
https://github.com/fvwmorg/fvwm/commit/7cfd209e17ed88c34f7ec9318dd82aabc3757baa
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/add_window.c

  Log Message:
  ---
  Improve and clean up size hints warnings.


  Commit: e98b3e7fae771ca0f6db4ef4c3102bc248a64a02
  
https://github.com/fvwmorg/fvwm/commit/e98b3e7fae771ca0f6db4ef4c3102bc248a64a02
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M modules/FvwmIconMan/xmanager.c

  Log Message:
  ---
  FvwmIconMan: Don't trigger size hints warning in fvwm core.


  Commit: 5ffc872c63fbd70db2dfc73042fe580fd7a57ec2
  
https://github.com/fvwmorg/fvwm/commit/5ffc872c63fbd70db2dfc73042fe580fd7a57ec2
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/events.c

  Log Message:
  ---
  Fix disappearing windows.

The old patch that removed synthetic UnmapNotify events on the root window to
suppress windows in HandeMapRequestKeepRaised() being unmapped later.  However,
this also caused problems.  vmplayer windows still diasppeared when returning
from fullscreen mode.

It seems that the real problem was the XUnmapWindow in HandleUnmapNotify.
Whoever thought this was a necessary or a good idea is wrong.  When we get an
UnmapNotify on a client window, the client has already unmapped it itself.
When we get a synthetic UnmapNotify on the root window the client has also
unmapped the window.  There's no need whatsoever to unmap it again, and events
caused by unmapping twice do confuse applications.


  Commit: ccea4a057b8dca8657da9f3a505022716ce91999
  
https://github.com/fvwmorg/fvwm/commit/ccea4a057b8dca8657da9f3a505022716ce91999
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS.


  Commit: 2db6922a298738568c3a012e5a62183efe543e48
  
https://github.com/fvwmorg/fvwm/commit/2db6922a298738568c3a012e5a62183efe543e48
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M bin/Makefile.am
M configure.ac
M doc/fvwm/Makefile.am
M fvwm/Makefile.am
M modules/FvwmAnimate/Makefile.am
M modules/FvwmAuto/Makefile.am
M modules/FvwmBacker/Makefile.am
M modules/FvwmBanner/Makefile.am
M modules/FvwmButtons/Makefile.am
R modules/FvwmCommand/FvwmCommandS.c
M modules/FvwmCommand/Makefile.am
A modules/FvwmCommandS/FvwmCommand.h
A modules/FvwmCommandS/FvwmCommandS.c
A modules/FvwmCommandS/Makefile.am
A modules/FvwmCommandS/fifos.c
M modules/FvwmConsole/Makefile.am
M modules/FvwmCpp/Makefile.am
M modules/FvwmEvent/Makefile.am
M modules/FvwmForm/Makefile.am
M modules/FvwmIconMan/Makefile.am
M modules/FvwmIdent/Makefile.am
M modules/FvwmM4/Makefile.am
M modules/FvwmPager/Makefile.am
M modules/FvwmPerl/Makefile.am
M modules/FvwmProxy/Makefile.am
M modules/FvwmRearrange/Makefile.am
M modules/FvwmScript/Makefile.am
M modules/Makefile.am

  Log Message:
  ---
  Fix installation and uninstallation with --program-transform-name.

Had to move FvwmCommandS to a different subdir to do this.


  Commit: 359820be6d7b85b9ceb796a7f1a03c964f08d9d2
  
https://github.com/fvwmorg/fvwm/commit/359820be6d7b85b9ceb796a7f1a03c964f08d9d2
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS.


Compare: https://github.com/fvwmorg/fvwm/compare/9a57db1dd4ae...359820be6d7b


[fvwmorg/fvwm] 7cfd20: Improve and clean up size hints warnings.

2016-12-28 Thread Dominik Vogt
  Branch: refs/heads/dv/devel
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 7cfd209e17ed88c34f7ec9318dd82aabc3757baa
  
https://github.com/fvwmorg/fvwm/commit/7cfd209e17ed88c34f7ec9318dd82aabc3757baa
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/add_window.c

  Log Message:
  ---
  Improve and clean up size hints warnings.


  Commit: e98b3e7fae771ca0f6db4ef4c3102bc248a64a02
  
https://github.com/fvwmorg/fvwm/commit/e98b3e7fae771ca0f6db4ef4c3102bc248a64a02
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M modules/FvwmIconMan/xmanager.c

  Log Message:
  ---
  FvwmIconMan: Don't trigger size hints warning in fvwm core.


  Commit: 5ffc872c63fbd70db2dfc73042fe580fd7a57ec2
  
https://github.com/fvwmorg/fvwm/commit/5ffc872c63fbd70db2dfc73042fe580fd7a57ec2
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M fvwm/events.c

  Log Message:
  ---
  Fix disappearing windows.

The old patch that removed synthetic UnmapNotify events on the root window to
suppress windows in HandeMapRequestKeepRaised() being unmapped later.  However,
this also caused problems.  vmplayer windows still diasppeared when returning
from fullscreen mode.

It seems that the real problem was the XUnmapWindow in HandleUnmapNotify.
Whoever thought this was a necessary or a good idea is wrong.  When we get an
UnmapNotify on a client window, the client has already unmapped it itself.
When we get a synthetic UnmapNotify on the root window the client has also
unmapped the window.  There's no need whatsoever to unmap it again, and events
caused by unmapping twice do confuse applications.


  Commit: ccea4a057b8dca8657da9f3a505022716ce91999
  
https://github.com/fvwmorg/fvwm/commit/ccea4a057b8dca8657da9f3a505022716ce91999
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS.


  Commit: 2db6922a298738568c3a012e5a62183efe543e48
  
https://github.com/fvwmorg/fvwm/commit/2db6922a298738568c3a012e5a62183efe543e48
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M bin/Makefile.am
M configure.ac
M doc/fvwm/Makefile.am
M fvwm/Makefile.am
M modules/FvwmAnimate/Makefile.am
M modules/FvwmAuto/Makefile.am
M modules/FvwmBacker/Makefile.am
M modules/FvwmBanner/Makefile.am
M modules/FvwmButtons/Makefile.am
R modules/FvwmCommand/FvwmCommandS.c
M modules/FvwmCommand/Makefile.am
A modules/FvwmCommandS/FvwmCommand.h
A modules/FvwmCommandS/FvwmCommandS.c
A modules/FvwmCommandS/Makefile.am
A modules/FvwmCommandS/fifos.c
M modules/FvwmConsole/Makefile.am
M modules/FvwmCpp/Makefile.am
M modules/FvwmEvent/Makefile.am
M modules/FvwmForm/Makefile.am
M modules/FvwmIconMan/Makefile.am
M modules/FvwmIdent/Makefile.am
M modules/FvwmM4/Makefile.am
M modules/FvwmPager/Makefile.am
M modules/FvwmPerl/Makefile.am
M modules/FvwmProxy/Makefile.am
M modules/FvwmRearrange/Makefile.am
M modules/FvwmScript/Makefile.am
M modules/Makefile.am

  Log Message:
  ---
  Fix installation and uninstallation with --program-transform-name.

Had to move FvwmCommandS to a different subdir to do this.


  Commit: 359820be6d7b85b9ceb796a7f1a03c964f08d9d2
  
https://github.com/fvwmorg/fvwm/commit/359820be6d7b85b9ceb796a7f1a03c964f08d9d2
  Author: Dominik Vogt 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M NEWS

  Log Message:
  ---
  NEWS.


Compare: https://github.com/fvwmorg/fvwm/compare/7cfd209e17ed^...359820be6d7b


Re: Fwd: Bug#849355: fvwm: GetWindowSizeHints warnings when windows and opened and closed

2016-12-28 Thread Dominik Vogt
On Tue, Dec 27, 2016 at 05:34:08PM -0700, Jaimos Skriletz wrote:
> On Tue, Dec 27, 2016 at 5:28 PM, Jaimos Skriletz
>  wrote:
> > On Tue, Dec 27, 2016 at 5:15 PM, Dominik Vogt  wrote:
> >> On Tue, Dec 27, 2016 at 05:04:40PM -0700, Jaimos Skriletz wrote:
> >>> On Tue, Dec 27, 2016 at 4:52 PM, Jaimos Skriletz
> >>>  wrote:
> >>> > On Tue, Dec 27, 2016 at 3:44 PM, Dominik Vogt  
> >>> > wrote:
> >>> >> On Mon, Dec 26, 2016 at 01:17:05PM -0700, Jaimos Skriletz wrote:
> >>> >>> Hello,
> >>> >>>
> >>> >>> This was reported by a Debian user. Please retain the CC to
> >>> >>> 849355-forwar...@bugs.debian.org in your response, so that
> >>> >>> the Debian BTS has a record.
> >>> >>>
> >>> >>> In short when running FvwmIconMan, fvwm prints warnings to stderr when
> >>> >>> opening and closing windows. I too have had this issue in 2.6.7 (and
> >>> >>> previous versions) so I can also say it affects my Debian system.
> >>> >>
> >>> >>
> >>> >> I don't get any such messages with or without FvwmIconMan.  Can
> >>> >> you give detailed instructions pelase?
> >>> >>
> >>> >
> >>> > Using Fvwm 2.6.7 Debian package, doubt it is any of the debian
> >>> > patches, but I will compile a version without patches and test.
> >>> >
> >>>
> >>> Tested with a fresh compile of Fvwm 2.6.7 without any debian patches,
> >>> same issue.
> >>>
> >>> >
> >>> > I tested this with other windows and modules. FvwmScript modules
> >>> > seemed to trigger it, FvwmIdentify did not, so I wonder if it has to
> >>> > do with transient windows or not (just something I noticed).
> >>> >
> >>>
> >>> Nevermind this, FvwmIdentify is not a traisnent window, the reason it
> >>> was not producing the warning was it was configured so FvwmIconMan did
> >>> not create a button for that window.
> >>>
> >>> After further testing the warning seems to be due to be caused by
> >>> adding/removing the button for a window from FvwmIconMan. Windows that
> >>> appear there trigger the warning but ones that don't appear don't.
> >>
> >> Still no luck to reproduce it.  After said message there should
> >> always be this one which prints all the details of the window and
> >> the faulty hints:
> >>
> >> fvwm_msg(
> >> WARN, "GetWindowSizeHints",
> >> "The application window (id %#lx)\n"
> >> "  \"%s\" has broken size hints (%s).\n"
> >> "fvwm is ignoring those hints.  "
> >> "  hint override = %d, flags = %lx\n"
> >> "  min_width = %d, min_height = %d, "
> >> "max_width = %d, max_height = %d\n"
> >> "  width_inc = %d, height_inc = %d\n"
> >> "  min_aspect = %d/%d, max_aspect = %d/%d\n"
> >> "  base_width = %d, base_height = %d\n"
> >> "  win_gravity = %d\n",
> >>
> >
> > I get no other output after the warning, so that message is never
> > printed to stderr on my system.
> >
> > Unsure if this helps, but I did enable BugOpts DebugCRMotionMethod,
> > and get the output
> >
> > _cdim: not moved 0x55927d4a8990 'FvwmIconMan'
> >
> > after each time the warning is produced.
> 
> Further testing, if I set the ManagerGeometry to something like 5x3 so
> FvwmIconMan doesn't resize itself, I no longer get the warning. It is
> only with the default like 0x1, causing the window to grow/shrink I
> get the warning.

Could be reproduced with a standalone FvwmIconMan (instead of the
one inside FvwmButtons).

> Wild guess, could it be some timing issue during the resizing of the
> window when adding/removing a button cause the window's current size
> to become invalid as per the warning?

Roughly, yes.  FvwmIconMan sets the minimum and maximum width and
height size hints to the new geometry it wants, then requests the
new size.  When fvwm reads the new hints, the current geometry of
the manager window becomes obviously invalid until the window is
also resized.  That's what triggers the warning.

So, to fix this:

1. Remove the size restrictions, then resize, then set the new
   size restrictions.  Theoretically the winodw might be resized
   by the user in between, but that's highly unlikely.

2. Also print the size hints that trigger this warning in a second
   message.

Fixed on the (new) fvwm2-stable branch; patch for the development
branches will follow one I've figured out how to deal with the
two repositories.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt



[fvwmorg/fvwm] 88de67: Add default-config to fvwm

2016-12-28 Thread Thomas Adam
  Branch: refs/heads/fvwm2-stable
  Home:   https://github.com/fvwmorg/fvwm
  Commit: 88de673f071678ee6255d638b9346555a9f30ff8
  
https://github.com/fvwmorg/fvwm/commit/88de673f071678ee6255d638b9346555a9f30ff8
  Author: Thomas Adam 
  Date:   2016-12-28 (Wed, 28 Dec 2016)

  Changed paths:
M Makefile.am
M configure.ac
A default-config/.stalonetrayrc
A default-config/FvwmScript-ConfirmCopyConfig
A default-config/FvwmScript-ConfirmQuit
A default-config/FvwmScript-DateTime
A default-config/Makefile.am
A default-config/config
A default-config/images/background/bg1.png
A default-config/images/background/bg2.png
A default-config/images/background/bg3.png
A default-config/images/bgicons/bg1.png
A default-config/images/bgicons/bg2.png
A default-config/images/bgicons/bg3.png
A default-config/images/fvwm-logo-small.png
A default-config/images/icons/apps.png
A default-config/images/icons/conf.png
A default-config/images/icons/help.png
A default-config/images/icons/programs.png
A default-config/images/icons/quit.png
A default-config/images/icons/refresh.png
A default-config/images/icons/restart.png
A default-config/images/icons/terminal.png
A default-config/images/icons/wallpaper.png
A default-config/images/icons/xterm.png
M doc/fvwm/configuration.xml
M fvwm/ConfigFvwmDefaults
M fvwm/fvwm.c
M perllib/Makefile.am

  Log Message:
  ---
  Add default-config to fvwm

It's been a long-time coming, but fvwm out-of-the-box now has an uptodate and
maintainable configuration file which will hopefully serve as a good basis for
users to customise, should they not have one of their own to start with.

A few tiny backend changes (by Thomas Adam) were required to plumb the config
into the existing infrastructure.

All credit for this goes to Jaimos Skriletz for this work, with some nice
feedback from the fvwm community at-large (mostly on #fvwm on freenode).