[fvwmorg/fvwm] 55a589: Change version to 3.0.0
Thomas Adam <[email protected]> Wed, 19 Oct 2022 15:16:21 -0700
| Newsgroups | gmane.comp.window-managers.fvwm.devel |
|---|---|
| Message-ID | <fvwmorg/fvwm/push/refs/tags/1.0.0/[email protected]> |
Branch: refs/tags/1.0.0=0D
Home: https://github.com/fvwmorg/fvwm=0D
Commit: 55a5893adb4e332a48578734dee31f8929f2f2ad=0D
https://github.com/fvwmorg/fvwm/commit/55a5893adb4e332a48578734dee3=
1f8929f2f2ad=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2018-07-28 (Sat, 28 Jul 2018)=0D
=0D
Changed paths:=0D
M .gitignore=0D
M TODO.md=0D
M bin/Makefile.am=0D
M configure.ac=0D
M doc/fvwm/Makefile.am=0D
M fvwm/Makefile.am=0D
R fvwm/fvwm.c=0D
A fvwm/fvwm3.c=0D
M libs/Makefile.am=0D
R libs/fvwmlib.c=0D
A libs/fvwmlib3.c=0D
M modules/FvwmAnimate/Makefile.am=0D
M modules/FvwmAuto/Makefile.am=0D
M modules/FvwmBacker/Makefile.am=0D
M modules/FvwmBanner/Makefile.am=0D
M modules/FvwmButtons/Makefile.am=0D
M modules/FvwmCommand/Makefile.am=0D
M modules/FvwmCommandS/Makefile.am=0D
M modules/FvwmConsole/Makefile.am=0D
M modules/FvwmCpp/Makefile.am=0D
M modules/FvwmEvent/Makefile.am=0D
M modules/FvwmForm/Makefile.am=0D
M modules/FvwmIconMan/Makefile.am=0D
M modules/FvwmIdent/Makefile.am=0D
M modules/FvwmM4/Makefile.am=0D
M modules/FvwmPager/Makefile.am=0D
M modules/FvwmProxy/Makefile.am=0D
M modules/FvwmRearrange/Makefile.am=0D
M modules/FvwmScript/Makefile.am=0D
M tests/hints/Makefile.am=0D
M utils/Makefile.am=0D
M utils/fvwm-version-str.sh=0D
=0D
Log Message:=0D
-----------=0D
Change version to 3.0.0=0D
=0D
Indicate this is fvwm-3.0.0=0D
=0D
(cherry picked from commit d58219c5c32f1e430db15d4bc0008a36239c3030)=0D
=0D
=0D
Commit: fbbac1fa9433a352ce56da4736dddfaaf760f2eb=0D
https://github.com/fvwmorg/fvwm/commit/fbbac1fa9433a352ce56da4736dd=
dfaaf760f2eb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2018-07-29 (Sun, 29 Jul 2018)=0D
=0D
Changed paths:=0D
A .clang-format=0D
=0D
Log Message:=0D
-----------=0D
Introduce .clang-format=0D
=0D
Add a basic example of .clang-format which will be used in the future to=0D=
apply consistent coding style to fvwm3.=0D
=0D
=0D
Commit: 45e0ef4b8e962073c53097a6cb0b819dac15beb3=0D
https://github.com/fvwmorg/fvwm/commit/45e0ef4b8e962073c53097a6cb0b=
819dac15beb3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2018-07-29 (Sun, 29 Jul 2018)=0D
=0D
Changed paths:=0D
M .gitignore=0D
=0D
Log Message:=0D
-----------=0D
Update .gitignore=0D
=0D
Bring .gitignore in line with fvwm3 specific files.=0D
=0D
=0D
Commit: 2d285828787eab6402f42b8e61c50693f57b6bc9=0D
https://github.com/fvwmorg/fvwm/commit/2d285828787eab6402f42b8e61c5=
0693f57b6bc9=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2018-07-29 (Sun, 29 Jul 2018)=0D
=0D
Changed paths:=0D
M configure.ac=0D
A contrib/coccinelle/cast.cocci=0D
M fvwm/add_window.c=0D
M fvwm/borders.c=0D
M fvwm/builtins.c=0D
M fvwm/colorset.c=0D
M fvwm/conditional.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_icons.c=0D
M fvwm/ewmh_names.c=0D
M fvwm/execcontext.c=0D
M fvwm/expand.c=0D
M fvwm/frame.c=0D
M fvwm/functions.c=0D
M fvwm/fvwm3.c=0D
M fvwm/infostore.c=0D
M fvwm/menuitem.c=0D
M fvwm/menus.c=0D
M fvwm/menustyle.c=0D
M fvwm/modconf.c=0D
M fvwm/module_interface.c=0D
M fvwm/module_list.c=0D
M fvwm/move_resize.c=0D
M fvwm/read.c=0D
M fvwm/schedule.c=0D
M fvwm/session.c=0D
M fvwm/stack.c=0D
M fvwm/style.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M fvwm/windowshade.c=0D
M libs/BidiJoin.c=0D
M libs/Bindings.c=0D
M libs/Colorset.c=0D
M libs/CombineChars.c=0D
M libs/FBidi.c=0D
M libs/FEvent.c=0D
M libs/FGettext.c=0D
M libs/FImage.c=0D
M libs/FScreen.c=0D
M libs/FTips.c=0D
M libs/Fft.c=0D
M libs/Ficonv.c=0D
M libs/Flocale.c=0D
M libs/FlocaleCharset.c=0D
M libs/Graphics.c=0D
M libs/Makefile.am=0D
M libs/Module.c=0D
M libs/Parse.c=0D
M libs/Picture.c=0D
M libs/PictureBase.c=0D
M libs/PictureGraphics.c=0D
M libs/PictureImageLoader.c=0D
M libs/PictureUtils.c=0D
M libs/Strings.c=0D
M libs/System.c=0D
M libs/XResource.c=0D
M libs/charmap.c=0D
M libs/envvar.c=0D
M libs/flist.c=0D
M libs/fsm.c=0D
M libs/queue.c=0D
M libs/safemalloc.c=0D
M libs/safemalloc.h=0D
A libs/strlcpy.c=0D
A libs/strlcpy.h=0D
M libs/timeout.c=0D
M modules/FvwmAnimate/FvwmAnimate.c=0D
M modules/FvwmAuto/FvwmAuto.c=0D
M modules/FvwmBacker/FvwmBacker.c=0D
M modules/FvwmBanner/FvwmBanner.c=0D
M modules/FvwmButtons/FvwmButtons.c=0D
M modules/FvwmButtons/FvwmButtons.h=0D
M modules/FvwmButtons/button.c=0D
M modules/FvwmButtons/parse.c=0D
M modules/FvwmCommand/FvwmCommand.c=0D
M modules/FvwmCommand/fifos.c=0D
M modules/FvwmCommandS/FvwmCommandS.c=0D
M modules/FvwmConsole/FvwmConsole.c=0D
M modules/FvwmConsole/FvwmConsoleC.c=0D
M modules/FvwmConsole/getline.c=0D
M modules/FvwmCpp/FvwmCpp.c=0D
M modules/FvwmEvent/FvwmEvent.c=0D
M modules/FvwmForm/FvwmForm.c=0D
M modules/FvwmForm/ParseCommand.c=0D
M modules/FvwmForm/ReadXServer.c=0D
M modules/FvwmIconMan/FvwmIconMan.c=0D
M modules/FvwmIconMan/functions.c=0D
M modules/FvwmIconMan/globals.c=0D
M modules/FvwmIconMan/readconfig.c=0D
M modules/FvwmIconMan/winlist.c=0D
M modules/FvwmIconMan/xmanager.c=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmM4/FvwmM4.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/x_pager.c=0D
M modules/FvwmProxy/FvwmProxy.c=0D
M modules/FvwmRearrange/FvwmRearrange.c=0D
M modules/FvwmScript/FvwmScript.c=0D
M modules/FvwmScript/Instructions.c=0D
M modules/FvwmScript/Widgets/Swallow.c=0D
M modules/FvwmScript/scanner.c=0D
M modules/FvwmScript/script.c=0D
M modules/FvwmScript/script.y=0D
=0D
Log Message:=0D
-----------=0D
Replace safemalloc with x* equivalents=0D
=0D
It's insane to have casts to malloc and other functions, so remove those.=
=0D
Whilst there, standardise the wrappers we use.=0D
=0D
The conversion is achieved via a coccinelle script.=0D
=0D
=0D
Commit: 7b8684385826d71b38be96f3c1a4e82c39aa4b38=0D
https://github.com/fvwmorg/fvwm/commit/7b8684385826d71b38be96f3c1a4=
e82c39aa4b38=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-14 (Sun, 14 Apr 2019)=0D
=0D
Changed paths:=0D
M configure.ac=0D
R modules/FvwmBanner/FvwmBanner.1.in=0D
R modules/FvwmBanner/FvwmBanner.c=0D
R modules/FvwmBanner/Makefile.am=0D
R modules/FvwmBanner/fvwm-logo-current.xbm=0D
R modules/FvwmBanner/fvwm-logo-current.xpm=0D
R modules/FvwmCommand/Changes=0D
R modules/FvwmCommand/FvwmCommand.1.in=0D
R modules/FvwmCommand/FvwmCommand.c=0D
R modules/FvwmCommand/FvwmCommand.h=0D
R modules/FvwmCommand/Makefile.am=0D
R modules/FvwmCommand/README=0D
R modules/FvwmCommand/fifos.c=0D
R modules/FvwmCommand/findcmd.pl=0D
R modules/FvwmCommand/scripts/Makefile.am=0D
R modules/FvwmCommand/scripts/ex-auto.pl=0D
R modules/FvwmCommand/scripts/ex-cascade.pl=0D
R modules/FvwmCommand/scripts/ex-grpmv.pl=0D
R modules/FvwmCommand/scripts/focus-Netscape.pl=0D
R modules/FvwmCommand/scripts/focus-link.1=0D
R modules/FvwmCommand/scripts/focus-link.pl=0D
R modules/FvwmCommand/scripts/push-away.pl=0D
R modules/FvwmCommand/scripts/test1.pl=0D
R modules/FvwmCommand/scripts/test2.sh=0D
R modules/FvwmCommandS/FvwmCommand.h=0D
R modules/FvwmCommandS/FvwmCommandS.c=0D
R modules/FvwmCommandS/Makefile.am=0D
R modules/FvwmCommandS/fifos.c=0D
R modules/FvwmCpp/FvwmCpp.1.in=0D
R modules/FvwmCpp/FvwmCpp.c=0D
R modules/FvwmCpp/FvwmCpp.h=0D
R modules/FvwmCpp/Makefile.am=0D
R modules/FvwmForm/Changes=0D
R modules/FvwmForm/FvwmForm-Capture=0D
R modules/FvwmForm/FvwmForm-Desktop=0D
R modules/FvwmForm/FvwmForm-Form=0D
R modules/FvwmForm/FvwmForm-QuitVerify=0D
R modules/FvwmForm/FvwmForm-Rlogin=0D
R modules/FvwmForm/FvwmForm-RootCursor=0D
R modules/FvwmForm/FvwmForm-RootCursor.pl=0D
R modules/FvwmForm/FvwmForm-Talk=0D
R modules/FvwmForm/FvwmForm-TalkHelp=0D
R modules/FvwmForm/FvwmForm-XDGMenuHelp=0D
R modules/FvwmForm/FvwmForm-XDGOptionsHelp=0D
R modules/FvwmForm/FvwmForm.1.in=0D
R modules/FvwmForm/FvwmForm.c=0D
R modules/FvwmForm/FvwmForm.h=0D
R modules/FvwmForm/Makefile.am=0D
R modules/FvwmForm/ParseCommand.c=0D
R modules/FvwmForm/ReadXServer.c=0D
R modules/FvwmM4/FvwmM4.1.in=0D
R modules/FvwmM4/FvwmM4.c=0D
R modules/FvwmM4/FvwmM4.h=0D
R modules/FvwmM4/Makefile.am=0D
R modules/FvwmProxy/ConfigFvwmProxyDefaults=0D
R modules/FvwmProxy/FvwmProxy.1.in=0D
R modules/FvwmProxy/FvwmProxy.c=0D
R modules/FvwmProxy/FvwmProxy.h=0D
R modules/FvwmProxy/Makefile.am=0D
M modules/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
Deprecation of modules=0D
=0D
This deprecates some module from FVWM:=0D
=0D
* FvwmBanner -- can use an external program for this;=0D
* FvwmCommand/FvwmCommandS -- will be replaced;=0D
* FvwmCpp /FvwmM4 -- old;=0D
* FvwmForm -- FvwmScript does enough of this for now;=0D
* FvwmProxy -- interesting experiment.=0D
=0D
=0D
Commit: 431019675cb6d147cfe3615824ecacb68614451d=0D
https://github.com/fvwmorg/fvwm/commit/431019675cb6d147cfe3615824ec=
acb68614451d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-14 (Sun, 14 Apr 2019)=0D
=0D
Changed paths:=0D
M Makefile.am=0D
M configure.ac=0D
R tests/FvwmButtons/FvwmButtons.sh=0D
R tests/Makefile.am=0D
R tests/README.test_options=0D
R tests/hints/Makefile.am=0D
R tests/hints/README=0D
R tests/hints/hints_test.c=0D
R tests/menus/README=0D
R tests/menus/icon1.xpm=0D
R tests/menus/icon2.xpm=0D
R tests/menus/icon3.xpm=0D
R tests/menus/install.menus=0D
R tests/menus/menus.read=0D
R tests/menus/sidepic.xpm=0D
R tests/perl/README=0D
R tests/perl/module-example=0D
R tests/perl/module-flash=0D
R tests/perl/module-tkdesker=0D
R tests/perl/module-trackertest=0D
R tests/perl/module-winlist=0D
R tests/perl/show-commands=0D
R tests/perl/xmessage.fpl=0D
R tests/perl/xmessage.ppp=0D
R tests/purify/README=0D
R tests/purify/install.purify=0D
R tests/purify/purify.fvwm2rc=0D
R tests/purify/purify.read=0D
R tests/purify/test.png=0D
R tests/purify/test1.xpm=0D
R tests/purify/test2.xpm=0D
R tests/purify/test3.xpm=0D
R tests/purify/windowshade.pl=0D
R tests/purify/xtrek_fed_e.xbm=0D
R tests/random/README=0D
R tests/random/mkrandomcfg.zsh=0D
R tests/test_options=0D
=0D
Log Message:=0D
-----------=0D
Deprectate tests/=0D
=0D
These are old and antiquated, and haven't been maintained in ages.=0D
=0D
=0D
Commit: 969ad67557b45d653b1a311929ac3c3a8199c62a=0D
https://github.com/fvwmorg/fvwm/commit/969ad67557b45d653b1a311929ac=
3c3a8199c62a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-14 (Sun, 14 Apr 2019)=0D
=0D
Changed paths:=0D
R INSTALL.md=0D
M Makefile.am=0D
M README.md=0D
R TODO.md=0D
M configure.ac=0D
A dev-docs/COMMANDS=0D
A dev-docs/DEVELOPERS.md=0D
A dev-docs/INSTALL.md=0D
A dev-docs/Makefile.am=0D
A dev-docs/PARSING.md=0D
A dev-docs/TODO.md=0D
R docs/COMMANDS=0D
R docs/DEVELOPERS.md=0D
R docs/Makefile.am=0D
R docs/PARSING.md=0D
=0D
Log Message:=0D
-----------=0D
Rename docs -> dev-docs=0D
=0D
Using the name "docs" when there's already a "doc" directory for man=0D
page commands, was always risky. This should make the distinction=0D
easier.=0D
=0D
=0D
Commit: ba2a0eebdce9e26ef60adb4426c93581a3b475ac=0D
https://github.com/fvwmorg/fvwm/commit/ba2a0eebdce9e26ef60adb4426c9=
3581a3b475ac=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-16 (Tue, 16 Apr 2019)=0D
=0D
Changed paths:=0D
M autogen.sh=0D
M dev-docs/INSTALL.md=0D
=0D
Log Message:=0D
-----------=0D
INSTALL: don't let autogen imply configure=0D
=0D
When running autogen.sh, don't imply ./configure -- this is an oddity=0D
in FVWM; no other package does this.=0D
=0D
=0D
Commit: c7b9fd0a311ed83d2f8cc294bf7c4bf044c6b6fa=0D
https://github.com/fvwmorg/fvwm/commit/c7b9fd0a311ed83d2f8cc294bf7c=
4bf044c6b6fa=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-16 (Tue, 16 Apr 2019)=0D
=0D
Changed paths:=0D
M .travis.yml=0D
=0D
Log Message:=0D
-----------=0D
TRAVIS: fix build=0D
=0D
=0D
Commit: 0efbd1b0366a81ebb01bc6157dcc0e59c58b88ee=0D
https://github.com/fvwmorg/fvwm/commit/0efbd1b0366a81ebb01bc6157dcc=
0e59c58b88ee=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-04-16 (Tue, 16 Apr 2019)=0D
=0D
Changed paths:=0D
M .travis.yml=0D
=0D
Log Message:=0D
-----------=0D
TRAVIS-CI: unset CFLAGS for configure=0D
=0D
When calling ./configure, unset CFLAGS so the compiler isn't confused.=0D=
=0D
=0D
Commit: d036d0eca0a3825f92d6bd6d3df9b6006ec34178=0D
https://github.com/fvwmorg/fvwm/commit/d036d0eca0a3825f92d6bd6d3df9=
b6006ec34178=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-05-06 (Mon, 06 May 2019)=0D
=0D
Changed paths:=0D
A dev-docs/NEW-COMMANDS.md=0D
=0D
Log Message:=0D
-----------=0D
WIP: NEW-COMMANDS.md=0D
=0D
=0D
Commit: 8dd75710299197a2beaa5bebe27b6b680641ea0d=0D
https://github.com/fvwmorg/fvwm/commit/8dd75710299197a2beaa5bebe27b=
6b680641ea0d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-05-13 (Mon, 13 May 2019)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README.md: update with link to NEW-COMMANDS.md=0D
=0D
=0D
Commit: 9e48dc3d1c944c99c2c31d88016560d5243bde7c=0D
https://github.com/fvwmorg/fvwm/commit/9e48dc3d1c944c99c2c31d880165=
60d5243bde7c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-05-16 (Thu, 16 May 2019)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README.md: add Coverity status=0D
=0D
=0D
Commit: 48a90a700dc0acfd6fcb7206d10c97503daea6af=0D
https://github.com/fvwmorg/fvwm/commit/48a90a700dc0acfd6fcb7206d10c=
97503daea6af=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-05-16 (Thu, 16 May 2019)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README.md: fix build status icon=0D
=0D
=0D
Commit: b241eb227b2e5473596753dcbf9c61a9190271a3=0D
https://github.com/fvwmorg/fvwm/commit/b241eb227b2e5473596753dcbf9c=
61a9190271a3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2019-05-23 (Thu, 23 May 2019)=0D
=0D
Changed paths:=0D
M dev-docs/TODO.md=0D
=0D
Log Message:=0D
-----------=0D
+.=0D
=0D
=0D
Commit: 16ee6fb9784f5d694eb711d54a6f9f203c3ae5b3=0D
https://github.com/fvwmorg/fvwm/commit/16ee6fb9784f5d694eb711d54a6f=
9f203c3ae5b3=0D
Author: Matt Bisson <[email protected]>=0D
Date: 2019-09-10 (Tue, 10 Sep 2019)=0D
=0D
Changed paths:=0D
M modules/FvwmIconMan/x.c=0D
=0D
Log Message:=0D
-----------=0D
Fix uninitialized variable in FvwmIconMan colorset loop.=0D
=0D
In FvwmIconMan, using colorsets to set various styles (e.g., PlainColorse=
t,=0D
SelectColorset, etc.) is broken. Essentially, background colors for one =
color=0D
end up being mapped to the shadow color of the previously used colorset. =
This=0D
is because the loop that calls fvwmlib_XCreateGC on the various colorsets=
does=0D
not happen to set the background color from the colorset inside the loop.=
This=0D
makes the code function OK with just one colorset, but adding a second co=
lorset=0D
in your settings causes problems.=0D
=0D
This change explicitly set the background color on the GC within the loop=
, so as=0D
to not carry forth the shadow color from the end of the previous iteratio=
n.=0D
=0D
=0D
Commit: 72ad48788abaadde8eaeff50d2c9eaf9ad9ddc7a=0D
https://github.com/fvwmorg/fvwm/commit/72ad48788abaadde8eaeff50d2c9=
eaf9ad9ddc7a=0D
Author: Oliver Hattshire <[email protected]>=0D
Date: 2019-10-21 (Mon, 21 Oct 2019)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
Use the correct travis-ci project=0D
=0D
=0D
Commit: 5b00a1937adb6705528700d405056f9ce4bcef25=0D
https://github.com/fvwmorg/fvwm/commit/5b00a1937adb6705528700d40505=
6f9ce4bcef25=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-01 (Wed, 01 Jan 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M doc/Makefile.am=0D
M doc/commands/Makefile.am=0D
R doc/fvwm-man.xsl=0D
R doc/fvwm.ent.in=0D
R doc/fvwm.xsl=0D
M doc/fvwm/Makefile.am=0D
R doc/fvwm/fvwm.man.xml=0D
A doc/fvwm/fvwm3.man.xml=0D
M doc/fvwm/sections=0D
A doc/fvwm3-man.xsl=0D
A doc/fvwm3.ent.in=0D
A doc/fvwm3.xsl=0D
=0D
Log Message:=0D
-----------=0D
docbook: fix man/html page generation=0D
=0D
Move some files around to reference fvwm3 when generating man pages and=0D=
HTML documentation.=0D
=0D
=0D
Commit: 39617f39063de7f950f99428d1a81ba07f2f2b03=0D
https://github.com/fvwmorg/fvwm/commit/39617f39063de7f950f99428d1a8=
1ba07f2f2b03=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/conditional.c=0D
=0D
Log Message:=0D
-----------=0D
conditional.c: remove spammy error message=0D
=0D
Some conditional error messages are far too spammy.=0D
=0D
=0D
Commit: 5c598337aad23d79d345b476704fd1331760db2a=0D
https://github.com/fvwmorg/fvwm/commit/5c598337aad23d79d345b476704f=
d1331760db2a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
Update README=0D
=0D
=0D
Commit: 1a966d5660d2f0ec409103a223e43fa52a8e1393=0D
https://github.com/fvwmorg/fvwm/commit/1a966d5660d2f0ec409103a223e4=
3fa52a8e1393=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/functable.c=0D
M fvwm/fvwm3.c=0D
M fvwm/placement.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Xinerama: Remove support for SLS and Solaris=0D
=0D
=0D
Commit: b78b46e1df58bc86f2e5d03b4c6854feb1317366=0D
https://github.com/fvwmorg/fvwm/commit/b78b46e1df58bc86f2e5d03b4c68=
54feb1317366=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/Makefile.am=0D
M fvwm/expand.c=0D
M fvwm/fvwm.h=0D
M fvwm/icons.c=0D
M fvwm/menus.c=0D
M fvwm/module_list.h=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/schedule.c=0D
M fvwm/style.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/FTips.c=0D
M libs/Makefile.am=0D
M libs/XError.c=0D
M libs/queue.c=0D
M modules/FvwmAuto/Makefile.am=0D
M modules/FvwmBacker/Makefile.am=0D
M modules/FvwmButtons/Makefile.am=0D
M modules/FvwmIconMan/Makefile.am=0D
M modules/FvwmIconMan/x.c=0D
M modules/FvwmIdent/Makefile.am=0D
M modules/FvwmPager/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
Support XRandR and remove Xinerama=0D
=0D
This crudely rips out Xinerama and in its place adds support for XrandR=0D=
instead.=0D
=0D
Screens are no longer referenced by a number, instead the display name of=
=0D
the output is needed, as defined by xrandr(1). The same goes for any=0D
geometry string specifiers in FVWM which might have referenced a screen,=0D=
such as:=0D
=0D
PositionPlacement 100+200x10+10@0=0D
=0D
The "@0" part of that must be changed.=0D
=0D
The API is kept intact as much as possible in libs/FScreen.[ch]; with a f=
ew=0D
deprecations which were Xinerama-specific and no longer needed. Previous=
=0D
screen specifiers used to differentiate at the API level:=0D
=0D
FSCREEN_XYPOS=0D
FSCREEN_CURRENT=0D
FSCREEN_PRIMARY=0D
FSCREEN_GLOBAL=0D
=0D
Global is now referenced by the output name of "global", and is also the=0D=
monitor used in the case where XRandR is not used. There is no longer th=
e=0D
concept of a primary output (which was only ever used in cases where it w=
as=0D
not known which monitor a window should be placed on.) CURRENT and XYPOS=
=0D
now also collapse into the same meaning, but the API hasn't (yet) been=0D=
updated to reflect that.=0D
=0D
There is also (at present), no support for XRRUpdateConfiguration() on th=
e=0D
root window, hence unplugging and changing the rotation of monitor is not=
=0D
supported at this time.=0D
=0D
=0D
Commit: adabacaa8dd8f2dac0f32330733ff43296813c4f=0D
https://github.com/fvwmorg/fvwm/commit/adabacaa8dd8f2dac0f32330733f=
f43296813c4f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M libs/Makefile.am=0D
A libs/fqueue.c=0D
A libs/fqueue.h=0D
R libs/queue.c=0D
M libs/queue.h=0D
=0D
Log Message:=0D
-----------=0D
Move libs/queue.[ch] to libs/fqueue.[ch]=0D
=0D
This makes way for BSD's TAILQ definitions in queue.h=0D
=0D
=0D
Commit: 239b024e566b395a25c805be6da08afc37648be7=0D
https://github.com/fvwmorg/fvwm/commit/239b024e566b395a25c805be6da0=
8afc37648be7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M bin/Makefile.am=0D
M contrib/coccinelle/cast.cocci=0D
M fvwm/add_window.c=0D
M fvwm/borders.c=0D
M fvwm/builtins.c=0D
M fvwm/colorset.c=0D
M fvwm/conditional.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_icons.c=0D
M fvwm/ewmh_names.c=0D
M fvwm/execcontext.c=0D
M fvwm/expand.c=0D
M fvwm/frame.c=0D
M fvwm/functable.c=0D
M fvwm/functions.c=0D
M fvwm/fvwm.h=0D
M fvwm/fvwm3.c=0D
M fvwm/icons.c=0D
M fvwm/infostore.c=0D
M fvwm/menuitem.c=0D
M fvwm/menus.c=0D
M fvwm/menustyle.c=0D
M fvwm/modconf.c=0D
M fvwm/module_interface.c=0D
M fvwm/module_list.c=0D
M fvwm/move_resize.c=0D
M fvwm/read.c=0D
M fvwm/schedule.c=0D
M fvwm/session.c=0D
M fvwm/stack.c=0D
M fvwm/style.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M fvwm/windowshade.c=0D
M libs/BidiJoin.c=0D
M libs/Bindings.c=0D
M libs/Colorset.c=0D
M libs/CombineChars.c=0D
M libs/FBidi.c=0D
M libs/FEvent.c=0D
M libs/FGettext.c=0D
M libs/FImage.c=0D
M libs/FScreen.c=0D
M libs/FTips.c=0D
M libs/Fft.c=0D
M libs/Ficonv.c=0D
M libs/Flocale.c=0D
M libs/FlocaleCharset.c=0D
M libs/Graphics.c=0D
M libs/Module.c=0D
M libs/Parse.c=0D
M libs/Picture.c=0D
M libs/PictureBase.c=0D
M libs/PictureGraphics.c=0D
M libs/PictureImageLoader.c=0D
M libs/PictureUtils.c=0D
M libs/Strings.c=0D
M libs/System.c=0D
M libs/XResource.c=0D
M libs/charmap.c=0D
M libs/envvar.c=0D
M libs/flist.c=0D
M libs/fqueue.c=0D
M libs/fsm.c=0D
M libs/safemalloc.c=0D
M libs/safemalloc.h=0D
M libs/timeout.c=0D
M modules/FvwmAnimate/FvwmAnimate.c=0D
M modules/FvwmAuto/FvwmAuto.c=0D
M modules/FvwmBacker/FvwmBacker.c=0D
M modules/FvwmButtons/FvwmButtons.c=0D
M modules/FvwmButtons/button.c=0D
M modules/FvwmButtons/parse.c=0D
M modules/FvwmConsole/FvwmConsole.c=0D
M modules/FvwmConsole/FvwmConsoleC.c=0D
M modules/FvwmConsole/getline.c=0D
M modules/FvwmEvent/FvwmEvent.c=0D
M modules/FvwmIconMan/FvwmIconMan.c=0D
M modules/FvwmIconMan/functions.c=0D
M modules/FvwmIconMan/globals.c=0D
M modules/FvwmIconMan/readconfig.c=0D
M modules/FvwmIconMan/winlist.c=0D
M modules/FvwmIconMan/xmanager.c=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/x_pager.c=0D
M modules/FvwmRearrange/FvwmRearrange.c=0D
M modules/FvwmRearrange/Makefile.am=0D
M modules/FvwmScript/FvwmScript.c=0D
M modules/FvwmScript/Instructions.c=0D
M modules/FvwmScript/Makefile.am=0D
M modules/FvwmScript/Widgets/Swallow.c=0D
M modules/FvwmScript/Widgets/TextField.c=0D
M modules/FvwmScript/scanner.c=0D
M modules/FvwmScript/script.c=0D
M modules/FvwmScript/script.y=0D
=0D
Log Message:=0D
-----------=0D
Replace safemalloc with x* requivalents=0D
=0D
It's insane to have casts to malloc and other functions, so remove those.=
=0D
Whilst there, standardise the wrappers we use. We need to be careful=0D
with the naming, as some conflicts can occur with libreadline (such as=0D=
x*()). Using fx*() should suffice.=0D
=0D
=0D
Commit: 3b18675971d71a17c88806faf7d4718366b9ddef=0D
https://github.com/fvwmorg/fvwm/commit/3b18675971d71a17c88806faf7d4=
718366b9ddef=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/fvwmlib3.c=0D
=0D
Log Message:=0D
-----------=0D
RandR: detect monitors better=0D
=0D
Rather than just looking at the CTRC, also look at the potential outputs=0D=
attached to it.=0D
=0D
=0D
Commit: ec7c6f9d3cc971cdfed1184cc1eab6ad775ed433=0D
https://github.com/fvwmorg/fvwm/commit/ec7c6f9d3cc971cdfed1184cc1ea=
b6ad775ed433=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
RandR: don't create GLOBAL if RandR present=0D
=0D
If RandR is present, don't create the global screen; this will=0D
eventually mean API changes to ascertain monitor coordinates.=0D
=0D
=0D
Commit: dcddd71c099c9c62706eeecad613d5285eace97f=0D
https://github.com/fvwmorg/fvwm/commit/dcddd71c099c9c62706eeecad613=
d5285eace97f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
Include no_of_screens=0D
=0D
=0D
Commit: 046e80d8606eae08cd906ce18b81716717720f30=0D
https://github.com/fvwmorg/fvwm/commit/046e80d8606eae08cd906ce18b81=
716717720f30=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/move_resize.c=0D
=0D
Log Message:=0D
-----------=0D
SnapAttraction: use RandR for screen edges=0D
=0D
When performing the calculations for screen snapping, use the dimensions=0D=
of the given monitors from RandR.=0D
=0D
=0D
Commit: 487a2e708bc957a6092258ea477f74d0600bd41d=0D
https://github.com/fvwmorg/fvwm/commit/487a2e708bc957a6092258ea477f=
74d0600bd41d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/fvwm3.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Support Randr RRScreenChangeNotify=0D
=0D
For now, when on screen change events occur, add a static command of=0D
"All PlaceAgain" to at least have the clients on screen.=0D
=0D
This will change in the future.=0D
=0D
=0D
Commit: 3546643bf123bd6aed4edcef79aa3c2a08df5551=0D
https://github.com/fvwmorg/fvwm/commit/3546643bf123bd6aed4edcef79aa=
3c2a08df5551=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/expansion.xml=0D
M fvwm/expand.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: add $[screen.count] for total screens found=0D
=0D
Add a variable which returns the total number of screens detected.=0D
=0D
=0D
Commit: 1a3c6e992e3c4406a96aa234030083a98a8cbf7b=0D
https://github.com/fvwmorg/fvwm/commit/1a3c6e992e3c4406a96aa2340300=
83a98a8cbf7b=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/fvwm.h=0D
M fvwm/move_resize.c=0D
M fvwm/screen.h=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: track monitor via fw=0D
=0D
Store the monitor the FvwmWindow is on in the relevant structure. Will=0D=
be useful later on for screen tracking.=0D
=0D
=0D
Commit: 1eb5328075ea161b65b9e622a703be176438b047=0D
https://github.com/fvwmorg/fvwm/commit/1eb5328075ea161b65b9e622a703=
be176438b047=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M modules/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
Modules: add FvwmConsole=0D
=0D
FvwmConsole shouldn't have gone missing.=0D
=0D
=0D
Commit: 90a0bbba16153363e4c190cc464ef220f70e94d6=0D
https://github.com/fvwmorg/fvwm/commit/90a0bbba16153363e4c190cc464e=
f220f70e94d6=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M .travis.yml=0D
=0D
Log Message:=0D
-----------=0D
TRAVIS-CI: update=0D
=0D
=0D
Commit: 555dfab655bf2fd077450252f04f93f5477288e0=0D
https://github.com/fvwmorg/fvwm/commit/555dfab655bf2fd077450252f04f=
93f5477288e0=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/icons.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
fscreen_scr_arg: use struct rather than union=0D
=0D
The fscreen_scr_arg as a union only makes sense if mouse reporting is=0D
used, but this isn't the case now, so use a struct instead.=0D
=0D
=0D
Commit: ee744bbe0e408bd9a5d29ed6b80f871dc710892d=0D
https://github.com/fvwmorg/fvwm/commit/ee744bbe0e408bd9a5d29ed6b80f=
871dc710892d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/modconf.c=0D
M fvwm/module_interface.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M modules/FvwmButtons/FvwmButtons.c=0D
M modules/FvwmButtons/parse.c=0D
M modules/FvwmIconMan/fvwm.c=0D
M modules/FvwmIconMan/readconfig.c=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmRearrange/FvwmRearrange.c=0D
M modules/FvwmScript/FvwmScript.c=0D
=0D
Log Message:=0D
-----------=0D
Deprecate XineramaString to modules=0D
=0D
No longer allow modules to request or understand which montior they're=0D=
on -- this will be sent down to them as part of the ConfigInfo string.=0D=
=0D
=0D
Commit: 77e61fa2c988ef896a58bd492d1039a9dcf7697e=0D
https://github.com/fvwmorg/fvwm/commit/77e61fa2c988ef896a58bd492d10=
39a9dcf7697e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmIdent/FvwmIdent.h=0D
=0D
Log Message:=0D
-----------=0D
Ident: Print monitor name selected window is on=0D
=0D
When using Ident to show information about a window, also print out the n=
ame=0D
of the monitor.=0D
=0D
(cherry picked from commit 34704fd0b8bbf462e286cc5da6af7480ab017ddd)=0D
=0D
=0D
Commit: 1e2d9914fa22d42be13fe84f2d1b8233f92dcb0e=0D
https://github.com/fvwmorg/fvwm/commit/1e2d9914fa22d42be13fe84f2d1b=
8233f92dcb0e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/module_interface.c=0D
M libs/vpacket.h=0D
=0D
Log Message:=0D
-----------=0D
CONFIGARGS: Include the monitor number=0D
=0D
Augment the CONFIGARGS macro to also include the monitor number of the=0D=
configured window. This will allow modules to easily ascertain monitor=0D=
information without the need to mangle a pointer to some struct montor *.=
=0D
=0D
(cherry picked from commit 7bc4eb3433304e848aaaacccdcf2044c6663723e)=0D
=0D
=0D
Commit: 21bafb88888c37747509d2d4a370f8b80867fa51=0D
https://github.com/fvwmorg/fvwm/commit/21bafb88888c37747509d2d4a370=
f8b80867fa51=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Introduce monitor_by_number()=0D
=0D
Rather than internal APIs relying on the name of monitors when looking up=
=0D
various things about them, instead assign each monitor an ID which can be=
used=0D
internally.=0D
=0D
This will also make things easier in the longer-term when trying to strea=
mline=0D
how RandR is going to be used, but for now this will make more sense in t=
erms of=0D
communicating monitor information with modules.=0D
=0D
(cherry picked from commit 4a64584a6e6334d812ce66262291a88e55aab605)=0D
=0D
=0D
Commit: 197f6f81d8e5b924ebf3644a0c2ea5b857e7c1eb=0D
https://github.com/fvwmorg/fvwm/commit/197f6f81d8e5b924ebf3644a0c2e=
a5b857e7c1eb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
M libs/FScreen.c=0D
M libs/fvwmlib3.c=0D
=0D
Log Message:=0D
-----------=0D
monitor_q: move initialistion to libification=0D
=0D
Don't initialise monitor_q from FVWM3's init routine. Insteaad, let the=0D=
FScreenInit() function handle this. In doing so, let fvwm3lib set up=0D
the screens, this allows modules to be able to use the screen interface.=0D=
=0D
=0D
Commit: 3a975caa97cf3505001a6218a2f0ab45c06d3c66=0D
https://github.com/fvwmorg/fvwm/commit/3a975caa97cf3505001a6218a2f0=
ab45c06d3c66=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmIdent/FvwmIdent.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmIdent: update for monitor calculations=0D
=0D
Update FvwmIdent to use new module interface.=0D
=0D
=0D
Commit: e1641199a1037d55a5385edc7d088bcd15f76689=0D
https://github.com/fvwmorg/fvwm/commit/e1641199a1037d55a5385edc7d08=
8bcd15f76689=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/move_resize.c=0D
=0D
Log Message:=0D
-----------=0D
add_window: update monitor for window=0D
=0D
When a window is mapped/recaptured, tell the window which monitor it is=0D=
on.=0D
=0D
=0D
Commit: 9abd73c10d71f61669cb51d9aad633afe7d07373=0D
https://github.com/fvwmorg/fvwm/commit/9abd73c10d71f61669cb51d9aad6=
33afe7d07373=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/conditional.c=0D
=0D
Log Message:=0D
-----------=0D
conditional: avoid zero-size malloc=0D
=0D
Don't malloc a window count of zero as malloc isn't designed for this.=0D=
=0D
=0D
Commit: 35e8199fb01544603e973503ebb25e544c814749=0D
https://github.com/fvwmorg/fvwm/commit/35e8199fb01544603e973503ebb2=
5e544c814749=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/move_resize.c=0D
=0D
Log Message:=0D
-----------=0D
MoveToScreen: fix calling API for named screen=0D
=0D
When using 'MoveToScreen <screen>', ensure that <screen> is looked up=0D
appropriately, and don't therefore assume the global screen.=0D
=0D
=0D
Commit: 0c14371ae7d2c56b2c9029360066d1b413e6cf93=0D
https://github.com/fvwmorg/fvwm/commit/0c14371ae7d2c56b2c9029360066=
d1b413e6cf93=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-02 (Thu, 02 Jan 2020)=0D
=0D
Changed paths:=0D
M doc/allCommands.html=0D
M doc/commands/BugOpts.xml=0D
M doc/commands/EdgeResistance.xml=0D
M doc/commands/Maximize.xml=0D
M doc/commands/Menu.xml=0D
M doc/commands/MoveToScreen.xml=0D
M doc/commands/Style.xml=0D
M doc/commands/WindowList.xml=0D
R doc/commands/Xinerama.xml=0D
R doc/commands/XineramaPrimaryScreen.xml=0D
R doc/commands/XineramaSls.xml=0D
R doc/commands/XineramaSlsScreens.xml=0D
R doc/commands/XineramaSlsSize.xml=0D
M doc/fvwm/conditionals.xml=0D
M doc/fvwm/ewmh.xml=0D
M doc/fvwm/expansion.xml=0D
M doc/fvwm/fvwm3.man.xml=0D
M doc/fvwm/multiScreen.xml=0D
M doc/fvwm/options.xml=0D
M doc/fvwm/sections=0D
M doc/fvwm/virtualDesktopCommands.xml=0D
R doc/fvwm/xinerama.xml=0D
M doc/groupedCommands.html=0D
M doc/util/cmds.txt=0D
M fvwm/windowlist.c=0D
=0D
Log Message:=0D
-----------=0D
RandR: update documentation=0D
=0D
Update the documentation to remove references to Xinerama.=0D
=0D
=0D
Commit: 50cc043f8fa58625d67fba56415c2a70cd0c9273=0D
https://github.com/fvwmorg/fvwm/commit/50cc043f8fa58625d67fba56415c=
2a70cd0c9273=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-06 (Mon, 06 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
Add PNG to version string if PNG present=0D
=0D
FVWM has a history of listing out the libraries it is linked to when=0D
given --version. Add PNG to this list so it's more obvious which image=0D=
libraries are in use.=0D
=0D
=0D
Commit: 50dab27308e69312710634b0c35c89f348f3fa2e=0D
https://github.com/fvwmorg/fvwm/commit/50dab27308e69312710634b0c35c=
89f348f3fa2e=0D
Author: domichel <[email protected]>=0D
Date: 2020-01-08 (Wed, 08 Jan 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
Fix converting of multi-images icon files.=0D
=0D
=0D
Commit: 08348a42bc08855d98954597f83673e0b0e056c2=0D
https://github.com/fvwmorg/fvwm/commit/08348a42bc08855d98954597f836=
73e0b0e056c2=0D
Author: zielaj <[email protected]>=0D
Date: 2020-01-27 (Mon, 27 Jan 2020)=0D
=0D
Changed paths:=0D
M dev-docs/NEW-COMMANDS.md=0D
=0D
Log Message:=0D
-----------=0D
Fixed a typo=0D
=0D
=0D
Commit: dc2ce58f5daa223f7445fe9bc1cae0eafc5c70d7=0D
https://github.com/fvwmorg/fvwm/commit/dc2ce58f5daa223f7445fe9bc1ca=
e0eafc5c70d7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M doc/allCommands.html=0D
A doc/commands/DesktopConfiguration.xml=0D
M doc/fvwm/fvwm3.man.xml=0D
A doc/fvwm/randr.xml=0D
M doc/fvwm/virtualDesktopCommands.xml=0D
M doc/groupedCommands.html=0D
M fvwm/add_window.c=0D
M fvwm/borders.c=0D
M fvwm/builtins.c=0D
M fvwm/commands.h=0D
M fvwm/conditional.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh.h=0D
M fvwm/ewmh_conf.c=0D
M fvwm/ewmh_events.c=0D
M fvwm/ewmh_intern.h=0D
M fvwm/ewmh_names.c=0D
M fvwm/expand.c=0D
M fvwm/focus.c=0D
M fvwm/functable.c=0D
M fvwm/fvwm3.c=0D
M fvwm/geometry.c=0D
M fvwm/icons.c=0D
M fvwm/menus.c=0D
M fvwm/misc.c=0D
M fvwm/modconf.c=0D
M fvwm/module_interface.c=0D
M fvwm/move_resize.c=0D
M fvwm/move_resize.h=0D
M fvwm/placement.c=0D
M fvwm/screen.h=0D
M fvwm/session.c=0D
M fvwm/stack.c=0D
M fvwm/update.c=0D
M fvwm/virtual.c=0D
M fvwm/virtual.h=0D
M fvwm/windowlist.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Outputs: allow for global or per-desk configurations=0D
=0D
Rather than assuming that desks and pages are common to all outputs FVWM=0D=
has detected via RandR, add an option to make this "global" or=0D
"per-desktop".=0D
=0D
Currently, the existing behaviour is to operate in a global mode,=0D
whereby a change of desk or page happens across all outputs. Sometimes=0D=
though, it's desirable to have desks/pages contained to the outputs=0D
their on.=0D
=0D
To achieve this, a new command 'DesktopConfiguration' has been created,=0D=
taking two options:=0D
=0D
* "global" -- not specific to one output, but applies switching=0D
desks/pages across all monitors=0D
* "per-monitor" -- makes desks/pages specific to each output such that=0D=
switching to a specific page or desks affects just that monitor and=0D=
no other.=0D
=0D
This command can be toggled between global and per-monitor while FVWM is=0D=
running and will act accordingly.=0D
=0D
FvwmPager has been modified and can be told which monitor to interact=0D
with. A new option, 'Monitor' has been added and takes the name of the=0D=
RandR output to react to.=0D
=0D
=0D
Commit: f1e7c98758f3017eea827cac1e63ced724d1b112=0D
https://github.com/fvwmorg/fvwm/commit/f1e7c98758f3017eea827cac1e63=
ced724d1b112=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
GotoDesk: add "next" as a shortcut for next desk=0D
=0D
The semantics of the GotoDesk command are confusing. Instead, add a=0D
shortcut called "next" which will move to the next defined desktop (the=0D=
limit is set via the DesktopName command), and wrap around if the limit=0D=
is reached.=0D
=0D
=0D
Commit: 7309e0a85618734d4a45c4332ef3a0554f2c6fbe=0D
https://github.com/fvwmorg/fvwm/commit/7309e0a85618734d4a45c4332ef3=
a0554f2c6fbe=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/conditional.c=0D
M fvwm/cursor.c=0D
M fvwm/events.c=0D
M fvwm/fvwm3.c=0D
M fvwm/screen.h=0D
M fvwm/virtual.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: pan-frames per monitor=0D
=0D
If DesktopConfiguration is set to per-monitor, put pan-frames around=0D
each monitor.=0D
=0D
=0D
Commit: cb51bf8ea4c48f255cc5745669f0372071a306b3=0D
https://github.com/fvwmorg/fvwm/commit/cb51bf8ea4c48f255cc5745669f0=
372071a306b3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/fvwm.h=0D
M fvwm/module_interface.c=0D
M fvwm/screen.h=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/queue.h=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
M modules/FvwmPager/x_pager.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmPager: update module packets=0D
=0D
=0D
Commit: d3a53672b9fcf0987bf21335b83c8e44b221fbba=0D
https://github.com/fvwmorg/fvwm/commit/d3a53672b9fcf0987bf21335b83c=
8e44b221fbba=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
Remove stray debug=0D
=0D
=0D
Commit: 4574f48263294609a4838d4af42164d93af409a6=0D
https://github.com/fvwmorg/fvwm/commit/4574f48263294609a4838d4af421=
64d93af409a6=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
FindScreenOfXY: handle negative offsets=0D
=0D
When working out the position of a given x/y coordinates, take negative=0D=
offsets (for example, if the window is off-screen) to be treated as=0D
absolute values, since they'll represent the intended screen to be on,=0D=
even if most of the window is placed outside of it.=0D
=0D
=0D
Commit: 022e7d12b363e080924d72d52f150f6ae7549003=0D
https://github.com/fvwmorg/fvwm/commit/022e7d12b363e080924d72d52f15=
0f6ae7549003=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
placement: fix monitor detection=0D
=0D
When using placement methods other than UnderMouse, reference an=0D
appropriate monitor to perform placement calculations; it's not always=0D=
going to be present via an assigned FvwmWindow struct.=0D
=0D
=0D
Commit: e9e5db5b1b8f333a34456bd849eccbb543520226=0D
https://github.com/fvwmorg/fvwm/commit/e9e5db5b1b8f333a34456bd849ec=
cbb543520226=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
default-config: remove references to old modules=0D
=0D
Remove references to FvwmBanner and FvwmForm as these modules no longer=0D=
exist. In the case of FvwmBanner, an external program such as feh(1)=0D
can be used. FvwmForm has been replaced by FvwmScript.=0D
=0D
=0D
Commit: e8a1f10ade319cd33c97ac6fe42ac6dc7f486775=0D
https://github.com/fvwmorg/fvwm/commit/e8a1f10ade319cd33c97ac6fe42a=
c6dc7f486775=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
M modules/FvwmPager/FvwmPager.c=0D
=0D
Log Message:=0D
-----------=0D
GCC: fix some warnings=0D
=0D
Keep GCC happy by fixing warnings.=0D
=0D
=0D
Commit: f4881decfa80bd7641eab85ce647aa358881226c=0D
https://github.com/fvwmorg/fvwm/commit/f4881decfa80bd7641eab85ce647=
aa358881226c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/frame.c=0D
M fvwm/geometry.c=0D
M fvwm/geometry.h=0D
M fvwm/move_resize.c=0D
M fvwm/update.c=0D
=0D
Log Message:=0D
-----------=0D
geometry: update callers to take FvwmWindow *=0D
=0D
Some geometry calculations need a monitor to work from. Update those=0D
callers to be able to take that from fw/t since that holds the correct=0D=
information.=0D
=0D
=0D
Commit: 2166ce76c13fcdf08cb6c07e29be053d54bf205c=0D
https://github.com/fvwmorg/fvwm/commit/2166ce76c13fcdf08cb6c07e29be=
053d54bf205c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
debug: remove and tidy up=0D
=0D
Remove some left over debug, no longer required.=0D
=0D
=0D
Commit: 5d77b9eba33d5afab16532663a745bb1a26c519f=0D
https://github.com/fvwmorg/fvwm/commit/5d77b9eba33d5afab16532663a74=
5bb1a26c519f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/builtins.c=0D
M fvwm/events.c=0D
M fvwm/screen.h=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Bugopts: add DebugRandR option=0D
=0D
This adds DebugRandR to BugOpts to enable reporting on what state the=0D
outputs tracked by FVWM are in.=0D
=0D
=0D
Commit: 5dc838bdcf2a739e8a5b88c991ae40f623afc9d3=0D
https://github.com/fvwmorg/fvwm/commit/5dc838bdcf2a739e8a5b88c991ae=
40f623afc9d3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
Plug memory leak=0D
=0D
Don't leak memory when dealing with RandR screen changes.=0D
=0D
=0D
Commit: e302c7742c5e5bb145696a701f6daa26478edcbb=0D
https://github.com/fvwmorg/fvwm/commit/e302c7742c5e5bb145696a701f6d=
aa26478edcbb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/builtins.c=0D
M fvwm/conditional.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_events.c=0D
M fvwm/expand.c=0D
M fvwm/focus.c=0D
M fvwm/fvwm.h=0D
M fvwm/fvwm3.c=0D
M fvwm/icons.c=0D
M fvwm/menus.c=0D
M fvwm/misc.c=0D
M fvwm/module_interface.c=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/screen.h=0D
M fvwm/style.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M modules/FvwmButtons/FvwmButtons.c=0D
M modules/FvwmButtons/FvwmButtons.h=0D
M modules/FvwmButtons/parse.c=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/x_pager.c=0D
M modules/FvwmRearrange/FvwmRearrange.c=0D
=0D
Log Message:=0D
-----------=0D
RandR: track subtypes for outputs=0D
=0D
When a given output changes size, or is disabled, ensure FVWM is better=0D=
informed so that it can adjust its view of which outputs are available=0D=
and what their sizes are.=0D
=0D
FVWM uses rectangle calculations to determine if a window should receive=0D=
focus. When monitors come and go, FVWM needs to reinstate its view of=0D=
these outputs and their rectangles, based on the screen size at the=0D
time.=0D
=0D
It's more complicated with `DesktopConfiguration per-monitor` due to the=0D=
width/height of the screen being different from one another,=0D
potentially.=0D
=0D
This change is big, and is littered with debug.=0D
=0D
Goes a long way to fixing Github Issue #16, #19.=0D
=0D
=0D
Commit: 583f976f387ddd88f395c3087b81d6511f3e28bb=0D
https://github.com/fvwmorg/fvwm/commit/583f976f387ddd88f395c3087b81=
d6511f3e28bb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
monitor_get_count: use stored monitors=0D
=0D
When counting how many monitors FVWM knows about (including inactive=0D
ones), use the TAILQ rather than a separate running total.=0D
=0D
=0D
Commit: f422dcb95e80928f91bd973415a28d810b4847e3=0D
https://github.com/fvwmorg/fvwm/commit/f422dcb95e80928f91bd973415a2=
8d810b4847e3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
HandleRRScreenChangeNotify: update fw geometry=0D
=0D
Tell the given fw its geometry again and update the screen. Might be=0D
important if a given output's dimensions have changed and the geometry=0D=
is no longer valid.=0D
=0D
=0D
Commit: 8c5e341ca15262851602ee404dde534265d9b74d=0D
https://github.com/fvwmorg/fvwm/commit/8c5e341ca15262851602ee404dde=
534265d9b74d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
Global monitor: init and reference correct monitor=0D
=0D
When dealing with parameter expansion, ensure we use an appropriate=0D
monitor. In the case of expanding variables such as $[desk.name<n>], it=0D=
was assumed that the fw->m pointer could be used. However, such=0D
variables don't operate in a window context, and hence, fw is NULL, so=0D=
use the current monitor instead.=0D
=0D
Additionally, when the global screen is in use via DesktopConfiguration,=0D=
ensure we update the changed virtual_scr to *ALL* monitors present,=0D
regardless of whether they're active.=0D
=0D
=0D
Commit: 47bc78ed07bc835817986affe88924b3623b785f=0D
https://github.com/fvwmorg/fvwm/commit/47bc78ed07bc835817986affe889=
24b3623b785f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
FindScreenofXY: handle detecting pages=0D
=0D
When working out a relative X/Y position of a window, ensure we take=0D
into account the page that a window is on, relative to the output's X/Y=0D=
location.=0D
=0D
This change modulos the coordinates based on the total widths/heights of=0D=
all outputs.=0D
=0D
=0D
Commit: daae341f062c5089d8c1cc0c2d53fa995a3e8eb1=0D
https://github.com/fvwmorg/fvwm/commit/daae341f062c5089d8c1cc0c2d53=
fa995a3e8eb1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
monitor_dump_state: indicate current page=0D
=0D
When dumping out the monitor state, print out the current pageX/pageY=0D
values.=0D
=0D
=0D
Commit: 5a97975b2eff1507fd20256c14cb23e8723b626b=0D
https://github.com/fvwmorg/fvwm/commit/5a97975b2eff1507fd20256c14cb=
23e8723b626b=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
MoveViewPort: per-monitor page switching=0D
=0D
When moving between pages, where DesktopConfiguration is per-monitor,=0D
skip over those windows which aren't on the current monitor.=0D
=0D
This fixes the pathological case, but likely breaks the Scroll command.=0D=
=0D
Goes someway to helping to address #17=0D
=0D
=0D
Commit: 51dd3aee0a8873eabc25aa5b788a61faf634adae=0D
https://github.com/fvwmorg/fvwm/commit/51dd3aee0a8873eabc25aa5b788a=
61faf634adae=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/fvwm3.c=0D
M fvwm/session.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
SessionState: handle multiple monitors=0D
=0D
Start writing out monitor information in to the state file, and provide=0D=
a monitor output helper function to do this. Using monitor output IDs=0D=
rather than a monitor name is more consistent.=0D
=0D
When loading the state file back in, move the call after monitors have=0D=
been initialised so that the monitor matching can work correctly.=0D
=0D
This addresses issue #20=0D
=0D
=0D
Commit: 16507ef76eeb0f9ddc5f50f42bb2c4b61ba928d1=0D
https://github.com/fvwmorg/fvwm/commit/16507ef76eeb0f9ddc5f50f42bb2=
c4b61ba928d1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-01-28 (Tue, 28 Jan 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
M fvwm/screen.h=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
GotoPage: honour global screen size for pages=0D
=0D
When handling page coordinates, irrespective of the setting for=0D
DesktopConfiguration, always use the combined widths and heights for the=0D=
attached monitors.=0D
=0D
Because pages have to handle mapped windows (that is, unlike switching=0D=
desks, windows are not unmapped), when switching pages, windows are=0D
moved in/out of view, depending on the page (rectangle) which is coming=0D=
in to view.=0D
=0D
In the case of DesktopConfiguration being 'per-monitor', we want to=0D
still use the global screen; those windows on different monitors which=0D=
aren't on the monitor we're actively paging for, will still be ignored.=0D=
=0D
This should go someway to addressing #20.=0D
=0D
=0D
Commit: cdb48d3ecf3a218071b08865844780aebc8e1815=0D
https://github.com/fvwmorg/fvwm/commit/cdb48d3ecf3a218071b088658447=
80aebc8e1815=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-02-15 (Sat, 15 Feb 2020)=0D
=0D
Changed paths:=0D
A .editorconfig=0D
M dev-docs/DEVELOPERS.md=0D
=0D
Log Message:=0D
-----------=0D
editorconfig: add default options file=0D
=0D
Use the editorconfig plugin mechanism to define indentation options,=0D
etc.=0D
=0D
=0D
Commit: d13cd69bbdfba6fb18e14af25c913c20c055aaee=0D
https://github.com/fvwmorg/fvwm/commit/d13cd69bbdfba6fb18e14af25c91=
3c20c055aaee=0D
Author: Anindya Mukherjee <[email protected]>=0D
Date: 2020-03-01 (Sun, 01 Mar 2020)=0D
=0D
Changed paths:=0D
M dev-docs/COMMANDS=0D
M dev-docs/DEVELOPERS.md=0D
M dev-docs/INSTALL.md=0D
M dev-docs/NEW-COMMANDS.md=0D
M dev-docs/PARSING.md=0D
M dev-docs/TODO.md=0D
=0D
Log Message:=0D
-----------=0D
fix minor typos=0D
=0D
fix more typos=0D
=0D
=0D
Commit: 7ea456653055670bb4cb17db569a778de39b7d33=0D
https://github.com/fvwmorg/fvwm/commit/7ea456653055670bb4cb17db569a=
778de39b7d33=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-03-04 (Wed, 04 Mar 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README: clarify fvwm3 operation status=0D
=0D
=0D
Commit: 111d3f0de1c340999b4b3bd2f75e467541ac2c50=0D
https://github.com/fvwmorg/fvwm/commit/111d3f0de1c340999b4b3bd2f75e=
467541ac2c50=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-03-04 (Wed, 04 Mar 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README: add shields=0D
=0D
Add some shields to show open issues and contributors.=0D
=0D
=0D
Commit: 6213e5ebc76c43da667b4b13012c09aa83a58bb7=0D
https://github.com/fvwmorg/fvwm/commit/6213e5ebc76c43da667b4b13012c=
09aa83a58bb7=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-03-19 (Thu, 19 Mar 2020)=0D
=0D
Changed paths:=0D
M .editorconfig=0D
M fvwm/menubindings.c=0D
M fvwm/menudim.h=0D
M fvwm/menuroot.h=0D
M fvwm/menus.c=0D
=0D
Log Message:=0D
-----------=0D
should not compare menu positions with screen width/height.=0D
=0D
=0D
Commit: c830c0b6e35ad63256cbfbdf3153a55b3e9f7b7b=0D
https://github.com/fvwmorg/fvwm/commit/c830c0b6e35ad63256cbfbdf3153=
a55b3e9f7b7b=0D
Author: Kleber Tarc=C3=ADsio <[email protected]>=0D
Date: 2020-04-11 (Sat, 11 Apr 2020)=0D
=0D
Changed paths:=0D
M libs/PictureGraphics.c=0D
=0D
Log Message:=0D
-----------=0D
Avoiding a deallocated reference=0D
=0D
Avoiding a deallocated reference=0D
=0D
=0D
Commit: e8c3efc53dcf5ffae5183c271accc1f38a6a5c69=0D
https://github.com/fvwmorg/fvwm/commit/e8c3efc53dcf5ffae5183c271acc=
c1f38a6a5c69=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-04-14 (Tue, 14 Apr 2020)=0D
=0D
Changed paths:=0D
M libs/Graphics.c=0D
=0D
Log Message:=0D
-----------=0D
fix broken positions when drawing 3d borders=0D
=0D
The original code always skips the top-right point and bottom-right=0D
point when drawing the border. This is almost invisible if the=0D
background colour is similar to hi and sh colour. However, when the=0D
background colour is very different from hi or sh (for example, flat=0D
borders), then borders appear to be corrupted.=0D
=0D
It also underflows when a is 1, in y+i+l-a.=0D
=0D
=0D
Commit: 32f625c6e4176285b80e9da32d0417657e6306da=0D
https://github.com/fvwmorg/fvwm/commit/32f625c6e4176285b80e9da32d04=
17657e6306da=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-29 (Wed, 29 Apr 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
README: rejig help/support=0D
=0D
Deprecate the "Questions, comments" section, in favour of "Help and=0D
Support". Also mention the Fvwm Forums.=0D
=0D
=0D
Commit: b2486f653aa31d1b7f6d2a2c8ade0127386efab0=0D
https://github.com/fvwmorg/fvwm/commit/b2486f653aa31d1b7f6d2a2c8ade=
0127386efab0=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M doc/commands/GotoDeskAndPage.xml=0D
M doc/commands/GotoPage.xml=0D
M fvwm/add_window.c=0D
M fvwm/conditional.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/focus.c=0D
M fvwm/geometry.c=0D
M fvwm/icons.c=0D
M fvwm/misc.c=0D
M fvwm/misc.h=0D
M fvwm/modconf.c=0D
M fvwm/module_interface.c=0D
M fvwm/module_interface.h=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/Module.h=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
M modules/FvwmPager/x_pager.c=0D
=0D
Log Message:=0D
-----------=0D
RandR: Go back to tracking global width/height=0D
=0D
When dealing with multiple monitors, record the width/height as being=0D
united as one screen, and not keep them separate. When dealing with=0D
multiple pages, the entire screen needs to be used, otherwise the=0D
offsets for those pages "leaks" on to other monitors.=0D
=0D
This change means that the GotoPage & GotoDeskAndPage commands have been=0D=
updated to accept a screen name, which is called from FvwmPager. If no=0D=
screen name is given then the current monitor is used.=0D
=0D
Because of how FVWM maintains its list of monitors, modules can no=0D
longer access FVWM's internal structure for monitor information.=0D
Rather, monitor information is sent to modules via ConfigInfo. Only=0D
FvwmPager makes use of this at the moment.=0D
=0D
This should go some way to fixing #22, if not entirely.=0D
=0D
=0D
Commit: 430629b0baef2b834a190bbf1584c99741e42943=0D
https://github.com/fvwmorg/fvwm/commit/430629b0baef2b834a190bbf1584=
c99741e42943=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/misc.c=0D
=0D
Log Message:=0D
-----------=0D
IsRectangleOnThisPage: skip desk check=0D
=0D
When deciding whether to focus a window, don't check the desk; may as=0D
well just focus the window anyway.=0D
=0D
=0D
Commit: e05d058e2a8ded223fd2d63ad9d61a9d40ad66ef=0D
https://github.com/fvwmorg/fvwm/commit/e05d058e2a8ded223fd2d63ad9d6=
1a9d40ad66ef=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
place_window: use correct monitor for StartsOnDesk=0D
=0D
Ensure the correct moinitor is used for StartsOnDesk.=0D
=0D
=0D
Commit: aab31dae88ed5288da981f6903b66c723d9f7e0c=0D
https://github.com/fvwmorg/fvwm/commit/aab31dae88ed5288da981f6903b6=
6c723d9f7e0c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
M fvwm/screen.h=0D
=0D
Log Message:=0D
-----------=0D
UPDATE_FVWM_SCREEN: don't mangle fw->Desk=0D
=0D
When updating which screen a window is on, don't trample over the Desk=0D=
which has already been set via things like StartsOn{Page,Desk}.=0D
Otherwise, the window's intended desk is overwritten with the current=0D
desk which is almost never what the user menat.=0D
=0D
Fixes #39=0D
=0D
=0D
Commit: db6c75df56142a9c7120e6eac257e647b9f67a94=0D
https://github.com/fvwmorg/fvwm/commit/db6c75df56142a9c7120e6eac257=
e647b9f67a94=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
A contrib/randr-tool/randr.c=0D
=0D
Log Message:=0D
-----------=0D
randr-tool: diagnostic cli tool=0D
=0D
This introduces a simple RandR command line tool to help diagnose events=0D=
which FVWM should be listening for.=0D
=0D
=0D
Commit: d07d1569dfbaf8a4ab4d26070cf982c904dcea8c=0D
https://github.com/fvwmorg/fvwm/commit/d07d1569dfbaf8a4ab4d26070cf9=
82c904dcea8c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_names.c=0D
M fvwm/fvwm3.c=0D
M fvwm/geometry.c=0D
M fvwm/module_interface.c=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/session.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: rejig assignments for outputs=0D
=0D
This is a (large) intermediary change as prep work to using RandR 1.5=0D
=0D
=0D
Commit: ee524930dfd6de8ad4bbd2a1210744d314c05d59=0D
https://github.com/fvwmorg/fvwm/commit/ee524930dfd6de8ad4bbd2a12107=
44d314c05d59=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_names.c=0D
M fvwm/fvwm3.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: default to 1.5 upwards=0D
=0D
When quering for monitors, use XRRGetMonitors() to derive outputs. This=0D=
allows for easier means for detecting displays from previous versions.=0D=
=0D
Because of this (and because it means multiple monitors can be treated=0D=
as one screen, a la Xinerama), we now can no longer assume that desktops=0D=
are the same on all screens.=0D
=0D
This change divorces desktop creation from being per-monitor, instead=0D
initialising a list of desktops once at startup (and changed via the=0D
DesktopName command), which is then assigned to all monitors. This=0D
change allows for greater flexibility when DesktopConfiguration is=0D
per-monitor. We no longer have to dance through numerous hoops.=0D
=0D
=0D
Commit: 541172b5f5773c6d61934eb83f9b172609939995=0D
https://github.com/fvwmorg/fvwm/commit/541172b5f5773c6d61934eb83f9b=
172609939995=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
placement: various monitor-tracking fixes=0D
=0D
Track the monitor the window is on, and add some debug.=0D
=0D
=0D
Commit: 51fab42f7039957ce9c89fc88015f6d4f1cd1558=0D
https://github.com/fvwmorg/fvwm/commit/51fab42f7039957ce9c89fc88015=
f6d4f1cd1558=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
=0D
Log Message:=0D
-----------=0D
pointer.screen: don't quote string=0D
=0D
When substituting $[pointer.screen], the string would end up quoted.=0D
Don't do this, because things like:=0D
=0D
Style XTerm InitialMapCommand MoveToScreen $[pointer.screen]=0D
=0D
would end up with a literal string:=0D
=0D
'HDMI-2'=0D
=0D
Which is not the desired output.=0D
=0D
=0D
Commit: 79d626ba890dd080f9dc3cd869e8991d5332497c=0D
https://github.com/fvwmorg/fvwm/commit/79d626ba890dd080f9dc3cd869e8=
991d5332497c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/placement.c=0D
M fvwm/virtual.c=0D
M modules/FvwmPager/x_pager.c=0D
=0D
Log Message:=0D
-----------=0D
Further monitor enhancements=0D
=0D
When dealing with window placement when mapping windows, ensure the=0D
correct screen is used. Previously, the current screen was used for=0D
some calculations, despite the fact that the operand window was on a=0D
different scree. This caused problems.=0D
=0D
Elsewhere, use the correct screen when appropriate to do so.=0D
=0D
=0D
Commit: 3e46020264b2208f295d504df1d1c2e385204c10=0D
https://github.com/fvwmorg/fvwm/commit/3e46020264b2208f295d504df1d1=
c2e385204c10=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M doc/allCommands.html=0D
M doc/commands/BugOpts.xml=0D
R doc/commands/Recapture.xml=0D
R doc/commands/RecaptureWindow.xml=0D
M doc/commands/Style.xml=0D
M doc/commands/UpdateDecor.xml=0D
M doc/fvwm/windowState.xml=0D
M doc/groupedCommands.html=0D
M doc/util/cmds.txt=0D
M doc/util/genAllCommands.pl=0D
M fvwm/add_window.c=0D
M fvwm/functable.c=0D
=0D
Log Message:=0D
-----------=0D
Deprecate Recapture/RecaptureWindow commands=0D
=0D
In developing per-desktop support, the Recapture commands were having to=0D=
be continually kept in line with respect to ensuring that the=0D
InitialMapCommand didn't run at the wrong time.=0D
=0D
These commands have been obsolete for some time, given that Decors apply=0D=
their updates to windows immediately, as do Style commands. The need to=0D=
visually refresh windows is unnecessary now.=0D
=0D
These commands can be put to rest.=0D
=0D
=0D
Commit: 6342c3e9beb1048efd6f4650be6931db57178096=0D
https://github.com/fvwmorg/fvwm/commit/6342c3e9beb1048efd6f4650be69=
31db57178096=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
=0D
Log Message:=0D
-----------=0D
window_setup: copy over monitor struct=0D
=0D
When recapturing (and hence setting up) a window -- if we've seen the=0D
monitor before, stash this in the recaptured window, so that we don't=0D
end up missing this information; the callers after this will assume that=0D=
the fw->m pointer has already been set up.=0D
=0D
=0D
Commit: 007e2d89dcd92a3f1dfe39bbb06c8103801b1117=0D
https://github.com/fvwmorg/fvwm/commit/007e2d89dcd92a3f1dfe39bbb06c=
8103801b1117=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
events: handle mapping between recaptures=0D
=0D
When restarting fvwm3 with existing windows, unconditionally deiconify=0D=
windows, and fix up mapping check.=0D
=0D
=0D
Commit: cdf9975b362bce8d85407f8ad6dc8c73a1a24e80=0D
https://github.com/fvwmorg/fvwm/commit/cdf9975b362bce8d85407f8ad6dc=
8c73a1a24e80=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
placement: don't alter desk during restarts/recaptures=0D
=0D
When checking the desk a window should be on, don't clobber this over=0D
restarts or recaptures.=0D
=0D
=0D
Commit: 86038344d4240469d86677ae3403ade0a3ba0671=0D
https://github.com/fvwmorg/fvwm/commit/86038344d4240469d86677ae3403=
ade0a3ba0671=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
session: make monitor checks more robust=0D
=0D
When restarting FVWM with existing windows, ensure the correct monitor=0D=
is assigned and propagated through the window structures, so that FVWM=0D=
doesn't need to recalculate them.=0D
=0D
=0D
Commit: b85766b360e2f4fc6ad403f659f11cf4571d1426=0D
https://github.com/fvwmorg/fvwm/commit/b85766b360e2f4fc6ad403f659f1=
1cf4571d1426=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/move_resize.c=0D
M fvwm/virtual.c=0D
M fvwm/virtual.h=0D
=0D
Log Message:=0D
-----------=0D
get_page_arguments: pass back monitor=0D
=0D
When dealing with pages on different desks to the one the pointer is on,=0D=
don't assume that the active monitor is the correct one.=0D
=0D
Because the page arguments are used to calculate the monitor, pass this=0D=
back as a pointer-return value, and use it.=0D
=0D
=0D
Commit: 485160a30fdd1b0a1d976d77a862b60a942e2ad5=0D
https://github.com/fvwmorg/fvwm/commit/485160a30fdd1b0a1d976d77a862=
b60a942e2ad5=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/ewmh.c=0D
M fvwm/module_interface.c=0D
M fvwm/move_resize.c=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
Remove stray debug=0D
=0D
=0D
Commit: 8e88bbc1c351542404baa2b5697cd3609277e352=0D
https://github.com/fvwmorg/fvwm/commit/8e88bbc1c351542404baa2b5697c=
d3609277e352=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M doc/commands/AddButtonStyle.xml=0D
M doc/commands/AddTitleStyle.xml=0D
M doc/commands/AddToDecor.xml=0D
M doc/commands/AddToFunc.xml=0D
M doc/commands/AddToMenu.xml=0D
M doc/commands/All.xml=0D
M doc/commands/AnimatedMove.xml=0D
M doc/commands/Any.xml=0D
M doc/commands/Asterisk.xml=0D
M doc/commands/Beep.xml=0D
M doc/commands/BorderStyle.xml=0D
M doc/commands/Break.xml=0D
M doc/commands/BugOpts.xml=0D
M doc/commands/BusyCursor.xml=0D
M doc/commands/ButtonState.xml=0D
M doc/commands/ButtonStyle.xml=0D
M doc/commands/ChangeDecor.xml=0D
M doc/commands/ChangeMenuStyle.xml=0D
M doc/commands/CleanupColorsets.xml=0D
M doc/commands/ClickTime.xml=0D
M doc/commands/Close.xml=0D
M doc/commands/ColorLimit.xml=0D
M doc/commands/ColormapFocus.xml=0D
M doc/commands/Colorset.xml=0D
M doc/commands/CopyMenuStyle.xml=0D
M doc/commands/Current.xml=0D
M doc/commands/CursorMove.xml=0D
M doc/commands/CursorStyle.xml=0D
M doc/commands/DefaultColors.xml=0D
M doc/commands/DefaultColorset.xml=0D
M doc/commands/DefaultFont.xml=0D
M doc/commands/DefaultIcon.xml=0D
M doc/commands/DefaultLayers.xml=0D
M doc/commands/Delete.xml=0D
M doc/commands/Deschedule.xml=0D
M doc/commands/Desk.xml=0D
M doc/commands/DesktopConfiguration.xml=0D
M doc/commands/DesktopName.xml=0D
M doc/commands/DesktopSize.xml=0D
M doc/commands/Destroy.xml=0D
M doc/commands/DestroyDecor.xml=0D
M doc/commands/DestroyFunc.xml=0D
M doc/commands/DestroyMenu.xml=0D
M doc/commands/DestroyMenuStyle.xml=0D
M doc/commands/DestroyModuleConfig.xml=0D
M doc/commands/DestroyStyle.xml=0D
M doc/commands/DestroyWindowStyle.xml=0D
M doc/commands/Direction.xml=0D
M doc/commands/Echo.xml=0D
M doc/commands/EchoFuncDefinition.xml=0D
M doc/commands/EdgeCommand.xml=0D
M doc/commands/EdgeLeaveCommand.xml=0D
M doc/commands/EdgeResistance.xml=0D
M doc/commands/EdgeScroll.xml=0D
M doc/commands/EdgeThickness.xml=0D
M doc/commands/Emulate.xml=0D
M doc/commands/EscapeFunc.xml=0D
M doc/commands/EwmhBaseStruts.xml=0D
M doc/commands/EwmhNumberOfDesktops.xml=0D
M doc/commands/Exec.xml=0D
M doc/commands/ExecUseShell.xml=0D
M doc/commands/FakeClick.xml=0D
M doc/commands/FakeKeypress.xml=0D
M doc/commands/FlipFocus.xml=0D
M doc/commands/Focus.xml=0D
M doc/commands/FocusStyle.xml=0D
M doc/commands/Function.xml=0D
M doc/commands/GlobalOpts.xml=0D
M doc/commands/GnomeShowDesks.xml=0D
M doc/commands/GotoDesk.xml=0D
M doc/commands/GotoDeskAndPage.xml=0D
M doc/commands/GotoPage.xml=0D
M doc/commands/HideGeometryWindow.xml=0D
M doc/commands/HilightColor.xml=0D
M doc/commands/HilightColorset.xml=0D
M doc/commands/IconFont.xml=0D
M doc/commands/IconPath.xml=0D
M doc/commands/Iconify.xml=0D
M doc/commands/IgnoreModifiers.xml=0D
M doc/commands/ImagePath.xml=0D
M doc/commands/InfoStoreAdd.xml=0D
M doc/commands/InfoStoreClear.xml=0D
M doc/commands/InfoStoreRemove.xml=0D
M doc/commands/KeepRc.xml=0D
M doc/commands/Key.xml=0D
M doc/commands/KillModule.xml=0D
M doc/commands/Layer.xml=0D
M doc/commands/LocalePath.xml=0D
M doc/commands/Lower.xml=0D
M doc/commands/Maximize.xml=0D
M doc/commands/Menu.xml=0D
M doc/commands/MenuStyle.xml=0D
M doc/commands/Module.xml=0D
M doc/commands/ModuleListenOnly.xml=0D
M doc/commands/ModulePath.xml=0D
M doc/commands/ModuleSynchronous.xml=0D
M doc/commands/ModuleTimeout.xml=0D
M doc/commands/Mouse.xml=0D
M doc/commands/Move.xml=0D
M doc/commands/MoveThreshold.xml=0D
M doc/commands/MoveToDesk.xml=0D
M doc/commands/MoveToPage.xml=0D
M doc/commands/MoveToScreen.xml=0D
M doc/commands/Next.xml=0D
M doc/commands/NoWindow.xml=0D
M doc/commands/None.xml=0D
M doc/commands/Nop.xml=0D
M doc/commands/OpaqueMoveSize.xml=0D
M doc/commands/Pick.xml=0D
M doc/commands/PipeRead.xml=0D
M doc/commands/PixmapPath.xml=0D
M doc/commands/PlaceAgain.xml=0D
M doc/commands/Plus.xml=0D
M doc/commands/PointerKey.xml=0D
M doc/commands/PointerWindow.xml=0D
M doc/commands/Popup.xml=0D
M doc/commands/Prev.xml=0D
M doc/commands/PrintInfo.xml=0D
M doc/commands/Quit.xml=0D
M doc/commands/QuitScreen.xml=0D
M doc/commands/QuitSession.xml=0D
M doc/commands/Raise.xml=0D
M doc/commands/RaiseLower.xml=0D
M doc/commands/Read.xml=0D
M doc/commands/Refresh.xml=0D
M doc/commands/RefreshWindow.xml=0D
M doc/commands/Repeat.xml=0D
M doc/commands/Resize.xml=0D
M doc/commands/ResizeMaximize.xml=0D
M doc/commands/ResizeMove.xml=0D
M doc/commands/ResizeMoveMaximize.xml=0D
M doc/commands/RestackTransients.xml=0D
M doc/commands/Restart.xml=0D
M doc/commands/SaveQuitSession.xml=0D
M doc/commands/SaveSession.xml=0D
M doc/commands/ScanForWindow.xml=0D
M doc/commands/Schedule.xml=0D
M doc/commands/Scroll.xml=0D
M doc/commands/SendToModule.xml=0D
M doc/commands/SetAnimation.xml=0D
M doc/commands/SetEnv.xml=0D
M doc/commands/Silent.xml=0D
M doc/commands/SnapAttraction.xml=0D
M doc/commands/SnapGrid.xml=0D
M doc/commands/State.xml=0D
M doc/commands/Stick.xml=0D
M doc/commands/StickAcrossDesks.xml=0D
M doc/commands/StickAcrossPages.xml=0D
M doc/commands/Stroke.xml=0D
M doc/commands/StrokeFunc.xml=0D
M doc/commands/Style.xml=0D
M doc/commands/TearMenuOff.xml=0D
M doc/commands/Test.xml=0D
M doc/commands/TestRc.xml=0D
M doc/commands/ThisWindow.xml=0D
M doc/commands/Title.xml=0D
M doc/commands/TitleStyle.xml=0D
M doc/commands/UnsetEnv.xml=0D
M doc/commands/UpdateDecor.xml=0D
M doc/commands/UpdateStyles.xml=0D
M doc/commands/Wait.xml=0D
M doc/commands/WarpToWindow.xml=0D
M doc/commands/WindowFont.xml=0D
M doc/commands/WindowId.xml=0D
M doc/commands/WindowList.xml=0D
M doc/commands/WindowShade.xml=0D
M doc/commands/WindowShadeAnimate.xml=0D
M doc/commands/WindowStyle.xml=0D
M doc/commands/WindowsDesk.xml=0D
M doc/commands/XSync.xml=0D
M doc/commands/XSynchronize.xml=0D
M doc/commands/XorPixmap.xml=0D
M doc/commands/XorValue.xml=0D
M doc/fvwm/authors.xml=0D
M doc/fvwm/bidirText.xml=0D
M doc/fvwm/bindings.xml=0D
M doc/fvwm/booleanArgs.xml=0D
M doc/fvwm/bugs.xml=0D
M doc/fvwm/builtinBindings.xml=0D
M doc/fvwm/colorGradients.xml=0D
M doc/fvwm/colorsets.xml=0D
M doc/fvwm/commands.xml=0D
M doc/fvwm/conditionals.xml=0D
M doc/fvwm/configuration.xml=0D
M doc/fvwm/copyright.xml=0D
M doc/fvwm/cpp.xml=0D
M doc/fvwm/environment.xml=0D
M doc/fvwm/ewmh.xml=0D
M doc/fvwm/execution.xml=0D
M doc/fvwm/expansion.xml=0D
M doc/fvwm/focus.xml=0D
M doc/fvwm/fonts.xml=0D
M doc/fvwm/icccm.xml=0D
M doc/fvwm/images.xml=0D
M doc/fvwm/m4.xml=0D
M doc/fvwm/menus.xml=0D
M doc/fvwm/miscCommands.xml=0D
M doc/fvwm/moduleCommands.xml=0D
M doc/fvwm/modules.xml=0D
M doc/fvwm/mwm.xml=0D
M doc/fvwm/options.xml=0D
M doc/fvwm/quoting.xml=0D
M doc/fvwm/scripting.xml=0D
M doc/fvwm/session.xml=0D
M doc/fvwm/sessionCommands.xml=0D
M doc/fvwm/shortcuts.xml=0D
M doc/fvwm/styleCommands.xml=0D
M doc/fvwm/synopsis.xml=0D
M doc/fvwm/userFunctions.xml=0D
M doc/fvwm/virtualDesktopCommands.xml=0D
M doc/fvwm/windowMovement.xml=0D
M doc/fvwm/windowState.xml=0D
M doc/fvwm/windowStyles.xml=0D
A doc/fvwm3.ent=0D
=0D
Log Message:=0D
-----------=0D
documentation: fixup link to fvwm.ent=0D
=0D
This has changed to fvwm3.ent=0D
=0D
=0D
Commit: 0c9c2b0a0826dc854b55be460f58d7c6ce066ccb=0D
https://github.com/fvwmorg/fvwm/commit/0c9c2b0a0826dc854b55be460f58=
d7c6ce066ccb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
global mode: switch to desk/page=0D
=0D
When toggling DesktopConfiguration from per-monitor to global, ensure=0D
that all other monitors are switched to the same desk/page as the=0D
current monitor.=0D
=0D
This means that when one switches to a new desk/page, the same starting=0D=
point is consistent.=0D
=0D
=0D
Commit: ab7315ef4dc0b240dc4a9f7adfcd5e47fc5011bb=0D
https://github.com/fvwmorg/fvwm/commit/ab7315ef4dc0b240dc4a9f7adfcd=
5e47fc5011bb=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/conditional.c=0D
=0D
Log Message:=0D
-----------=0D
conditional: fix parsing of 'Screen'=0D
=0D
When reading in the name of an output to test, ensure the string buffer=0D=
is allocated first.=0D
=0D
=0D
Commit: cf96e02f661ea55010f6eb436e76d7331d093132=0D
https://github.com/fvwmorg/fvwm/commit/cf96e02f661ea55010f6eb436e76=
d7331d093132=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
=0D
Log Message:=0D
-----------=0D
used_sm: skip setup of maximized windows=0D
=0D
Previous to the change of recapturing windows, it was necessary to=0D
reinstate the max dimensions of a maximized window. As this happens on=0D=
LoadState now, there's no longer a need to that afterwards in the=0D
used_sm checks.=0D
=0D
=0D
Commit: 6a2c16351dd0994e4d48af72864893c27d417c39=0D
https://github.com/fvwmorg/fvwm/commit/6a2c16351dd0994e4d48af728648=
93c27d417c39=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
=0D
Log Message:=0D
-----------=0D
AddWindow: set monitor for global screen=0D
=0D
If `DesktopConfiguration` is `global`, set the monitor that the window=0D=
is on. Even though desktops aren't per-monitor, if this configuration=0D=
option changes, then we won't need to recalculate the screen again.=0D
=0D
=0D
Commit: 6de2d3be2eb6cd60808e76729468929c13a24bea=0D
https://github.com/fvwmorg/fvwm/commit/6de2d3be2eb6cd60808e76729468=
929c13a24bea=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
gotodesk: update all monitors when in global mode=0D
=0D
When switching to a new desk, if the DesktopsConfiguration is global=0D
make sure that all outputs are told about which page they need to be on,=0D=
and also which is the current monitor.=0D
=0D
=0D
Commit: 2632151caa5d1c11e9bafb48c8ef0648d6719db7=0D
https://github.com/fvwmorg/fvwm/commit/2632151caa5d1c11e9bafb48c8ef=
0648d6719db7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
StartsOnScreen: honour expanded variables=0D
=0D
With FVWM3 being per-monitor aware, there is now a need to be able to=0D
specify the current screen. However, since that is dynamic, we need to=0D=
ensure that the expansion of the current screen happens just in time.=0D
=0D
For example:=0D
=0D
Style foo StartsOnScreen $[ponter.screen]=0D
=0D
won't work, because when FVWM reads in that line from its config, it=0D
will have expanded $[pointer.screen] to be whatever value is correct at=0D=
that time, which means any window named "foo" would start on an=0D
incorrect screen.=0D
=0D
Therefore, support expansion of variables at the point we need them for=0D=
StartOnScreen.=0D
=0D
To achieve this, the following line would be needed:=0D
=0D
Style foo StartsOnScreen $$[pointer.screen]=0D
=0D
Which would mean that on the first pass, FVWM would have used:=0D
=0D
Style foo StartsOnScreen $[pointer.screen]=0D
=0D
... and then when the value for 'StartsOnScreen' is used, it will=0D
expand $[pointer.screen] to the name of a monitor.=0D
=0D
=0D
Commit: 1ab973b6d2c0647d2e8b55eaf780b507d590bac3=0D
https://github.com/fvwmorg/fvwm/commit/1ab973b6d2c0647d2e8b55eaf780=
b507d590bac3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
=0D
Log Message:=0D
-----------=0D
expand: don't quote W_SCREEN=0D
=0D
Don't explicitly quote the output from $[w.screen] as FVWM's parser will=0D=
treat the literal string 'HDMI1' as an output name, which is incorrect.=0D=
=0D
=0D
Commit: 19c220e0094ee4eef6f038ec74dbf506b5ed445e=0D
https://github.com/fvwmorg/fvwm/commit/19c220e0094ee4eef6f038ec74db=
f506b5ed445e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/style.c=0D
=0D
Log Message:=0D
-----------=0D
StartsOnScreen: retain backwards-compat with fvwm2=0D
=0D
Allow for the single character 'c' to mean the current monitor.=0D
=0D
=0D
Commit: 5b9a891bac14b29d1c461aec0c520d4ef9d8f473=0D
https://github.com/fvwmorg/fvwm/commit/5b9a891bac14b29d1c461aec0c52=
0d4ef9d8f473=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-04-30 (Thu, 30 Apr 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
MapRequest: fix IS_MAPPED check=0D
=0D
Fix a typo where a mapped window check was negative, causing windows not=0D=
to show up.=0D
=0D
=0D
Commit: 4f5cfc481b25cff299c0c0c00dd27b7a4a4ddb7d=0D
https://github.com/fvwmorg/fvwm/commit/4f5cfc481b25cff299c0c0c00dd2=
7b7a4a4ddb7d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-02 (Sat, 02 May 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
FScreenParseGeometry: fix negative offsets=0D
=0D
When parsing geometry strings, ensure the "global" screen is taken in to=0D=
account. Prior to this, the individual monitor was assumed.=0D
=0D
This should fix GH issue #28.=0D
=0D
=0D
Commit: a8e9c6ffe190d2ffd3a778953a294ed7da5a4c13=0D
https://github.com/fvwmorg/fvwm/commit/a8e9c6ffe190d2ffd3a778953a29=
4ed7da5a4c13=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-02 (Sat, 02 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
=0D
Log Message:=0D
-----------=0D
WorkArea: use screen dimensions to compute area=0D
=0D
When working out the working area for a desktop, use the monitor's=0D
coordinates (width/height) and not the XServer's display width or height=0D=
as these will differ.=0D
=0D
Fixes GH issue #52=0D
=0D
=0D
Commit: e24deb4bcfec60e7aea4b67ecc6eb18c0195ac4c=0D
https://github.com/fvwmorg/fvwm/commit/e24deb4bcfec60e7aea4b67ecc6e=
b18c0195ac4c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-02 (Sat, 02 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: respect the primary output=0D
=0D
When working out where to place windows, ensure we make use of the=0D
primary monitor. This can be accessed via the $[monitor.primary]=0D
variable. For example:=0D
=0D
Style * StartsOnScreen $$[monitor.primary]=0D
=0D
Helps fix GH issue #28=0D
=0D
=0D
Commit: 6cd13e894d40dc909971f21a73040b45794f67e9=0D
https://github.com/fvwmorg/fvwm/commit/6cd13e894d40dc909971f21a7304=
0b45794f67e9=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-03 (Sun, 03 May 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/expansion.xml=0D
=0D
Log Message:=0D
-----------=0D
expansion: document $[monitor.primary]=0D
=0D
Mention what $[monitor.primary] is used for.=0D
=0D
=0D
Commit: 58773edf4ac1a446a23801ac56b8fa7c9d938692=0D
https://github.com/fvwmorg/fvwm/commit/58773edf4ac1a446a23801ac56b8=
fa7c9d938692=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-03 (Sun, 03 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
MapWindow: honour iconification state=0D
=0D
Don't deiconify windows which are already iconified.=0D
=0D
=0D
Commit: 797592203447f39519de38a3f78b2675ecd40ba1=0D
https://github.com/fvwmorg/fvwm/commit/797592203447f39519de38a3f78b=
2675ecd40ba1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-04 (Mon, 04 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/move_resize.c=0D
=0D
Log Message:=0D
-----------=0D
SnapAttraction: fix coord detection=0D
=0D
Don't use per-monitor configuration when performing snapattraction=0D
calculations; windows can span across monitors.=0D
=0D
Fixes GH issue #61=0D
=0D
=0D
Commit: 8da96cae8616ad74d8da276569cb247efa69218e=0D
https://github.com/fvwmorg/fvwm/commit/8da96cae8616ad74d8da276569cb=
247efa69218e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-04 (Mon, 04 May 2020)=0D
=0D
Changed paths:=0D
A .github/workflows/ccpp.yml=0D
=0D
Log Message:=0D
-----------=0D
Create github action script=0D
=0D
This adds a new github action script to use GH's native CI, rather than t=
ravis-ci.=0D
=0D
=0D
Commit: 29e9a8a38a503befd09a39bf35a12b712f638cc3=0D
https://github.com/fvwmorg/fvwm/commit/29e9a8a38a503befd09a39bf35a1=
2b712f638cc3=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/move_resize.c=0D
=0D
Log Message:=0D
-----------=0D
unmaximize: use window's current screen for positioning=0D
=0D
When moving a maximized window between pages or screens, FVWM records=0D
the previous geometry of the unmaximized window, so it can restore=0D
correctly.=0D
=0D
However, this doesn't work well when the maximized window itself has=0D
moved between screens or different pages, since the unmaximized geometry=0D=
from the point of view of the maximized window is now incorrect.=0D
Subsequently, unmaximizing a window will put that window in to the=0D
ether.=0D
=0D
For now, the approach is to make unmaximizing a window imply=0D
MoveToScreen (relative to the window's screen) such that it remains=0D
visible, and should largely do what the user expects.=0D
=0D
Fixes #68=0D
=0D
=0D
Commit: 24b2b46c321dc64b84d1d1c080b87bbc26ecd60a=0D
https://github.com/fvwmorg/fvwm/commit/24b2b46c321dc64b84d1d1c080b8=
7bbc26ecd60a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M .github/workflows/ccpp.yml=0D
=0D
Log Message:=0D
-----------=0D
gh workflows: remove sending PR messages=0D
=0D
These clutter up IRC too much.=0D
=0D
Fixes #71=0D
=0D
=0D
Commit: 59c84cb646ca0d47bbcca8081e1ece24dcfa92a8=0D
https://github.com/fvwmorg/fvwm/commit/59c84cb646ca0d47bbcca8081e1e=
ce24dcfa92a8=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/screen.h=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
UPDATE_FVWM_SCREEN: remove win_count functionality=0D
=0D
In previous iterations of tracking which screen a given window was on,=0D=
or moved to, the assigned struct monitor would maintain a count of the=0D=
number of its windows.=0D
=0D
This was meant to provide functionality which is not going to be used=0D
now, so this can be removed.=0D
=0D
Fixes #70=0D
=0D
=0D
Commit: 0bea8d511f38e47c217b4bfc2a71a58a9f429a67=0D
https://github.com/fvwmorg/fvwm/commit/0bea8d511f38e47c217b4bfc2a71=
a58a9f429a67=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
=0D
Log Message:=0D
-----------=0D
Debug=0D
=0D
=0D
Commit: a77c29a659b220eacfbee0873f45fbd7819e8575=0D
https://github.com/fvwmorg/fvwm/commit/a77c29a659b220eacfbee0873f45=
fbd7819e8575=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
=0D
Log Message:=0D
-----------=0D
GetWorkAreaIntersection - fix for XRandR=0D
=0D
Don't cull the width/height of the intersection when the coords approach =
0, as=0D
this is a legitimate offset for the boundaries of the next rectangle.=0D
=0D
=0D
Commit: 5e2d8b3995b452e91e35148913b2cbd8ee4d0b6a=0D
https://github.com/fvwmorg/fvwm/commit/5e2d8b3995b452e91e35148913b2=
cbd8ee4d0b6a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_conf.c=0D
M fvwm/ewmh_events.c=0D
M fvwm/update.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
ewmhInfo: move into struct monitor, update callers=0D
=0D
Remove the extern ewmhc definition, moving it into struct monitor so that=
it can=0D
be referenced on a per-monitor basis.=0D
=0D
In doing this, and because certain callers assumed ewmhc was global, rewo=
rk them=0D
to get the values out the appropriate monitor.=0D
=0D
=0D
Commit: 31e69d357c4bfb95c3cd4b5b0b1b2ea623d4f238=0D
https://github.com/fvwmorg/fvwm/commit/31e69d357c4bfb95c3cd4b5b0b1b=
2ea623d4f238=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh.h=0D
M fvwm/ewmh_conf.c=0D
M fvwm/ewmh_events.c=0D
M fvwm/placement.c=0D
M fvwm/update.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
EWMH: make most things per-monitor aware=0D
=0D
When setting EWMH-atoms, use the monitor information to set height/width=0D=
values, etc.=0D
=0D
=0D
Commit: 1128b2289881e733b3de0c5a1e89640718a74d90=0D
https://github.com/fvwmorg/fvwm/commit/1128b2289881e733b3de0c5a1e89=
640718a74d90=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/ewmh_names.c=0D
M fvwm/virtual.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
Desktops: rework desktop assignment=0D
=0D
Rather than have a single reference desktop whose values are copied=0D
over, instead recompute Desktop per output.=0D
=0D
=0D
Commit: f8a20ab4ae5e0534649fff8b397bf7f50d433bb1=0D
https://github.com/fvwmorg/fvwm/commit/f8a20ab4ae5e0534649fff8b397b=
f7f50d433bb1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/virtual.c=0D
M fvwm/virtual.h=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
EWMHBaseStruts: init across monitors=0D
=0D
When starting new monitors, correctly reference the page sizes of the=0D
monitor, and propagate those values.=0D
=0D
=0D
Commit: 1fe6804b84727eec6289dd707cd87bfbc354d36f=0D
https://github.com/fvwmorg/fvwm/commit/1fe6804b84727eec6289dd707cd8=
7bfbc354d36f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/ewmh.h=0D
M fvwm/ewmh_conf.c=0D
=0D
Log Message:=0D
-----------=0D
EWMH: new monitor should apply basestruts=0D
=0D
When FVWM has detected a new monitor, apply the basestruts to it as a=0D
default.=0D
=0D
=0D
Commit: 04a3df1c8879580a2c8957136ba37bd3e8f19e00=0D
https://github.com/fvwmorg/fvwm/commit/04a3df1c8879580a2c8957136ba3=
7bd3e8f19e00=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
M fvwm/geometry.c=0D
M fvwm/move_resize.c=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
EWMH Intersection: use full display width/height=0D
=0D
When calculating the EWMHBaseStrutHints, map via the global display=0D
width and height.=0D
=0D
This also adds debug.=0D
=0D
=0D
Commit: 4ebab08f1f5b35249b3bfd8df9fb7688891c3733=0D
https://github.com/fvwmorg/fvwm/commit/4ebab08f1f5b35249b3bfd8df9fb=
7688891c3733=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh_conf.c=0D
=0D
Log Message:=0D
-----------=0D
EWMHBaseStruts: fix screen parsing=0D
=0D
If the monitor cannot be found, error, rather than assigning the current=0D=
monitor, which would otherwise have set incorrect values.=0D
=0D
=0D
Commit: 41dc6c3689d72492e7426a823684a7c5dbec3a6c=0D
https://github.com/fvwmorg/fvwm/commit/41dc6c3689d72492e7426a823684=
a7c5dbec3a6c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_conf.c=0D
M fvwm/virtual.c=0D
M fvwm/virtual.h=0D
=0D
Log Message:=0D
-----------=0D
CMD_DesktopName: split into helper functions=0D
=0D
Prior to this change, m->DesktopsInfo used a shared pointer to perform a=0D=
shallow copy of a reference monitor's desktop information. This was=0D
primarily used to copy over the names of desktops without the need to=0D
reparse.=0D
=0D
However, this will break the ability to set per-screen EWMHBaseStrut=0D
settings since now, the pointer is the same across all monitors, and=0D
they shouldn't be.=0D
=0D
So split out the parsing of CMD_DesktopName in to helper functions to=0D
make this easier to apply independantly across monitors.=0D
=0D
=0D
Commit: 84499a61dfb37e6f8f2e419cc4a76266d15e8f7a=0D
https://github.com/fvwmorg/fvwm/commit/84499a61dfb37e6f8f2e419cc4a7=
6266d15e8f7a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-09 (Sat, 09 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/borders.c=0D
=0D
Log Message:=0D
-----------=0D
border redraw: remove desk check=0D
=0D
Always redraw borders for windows which could otherwise be between=0D
desks.=0D
=0D
=0D
Commit: 3f3ad36421096ef77804fd84fa337338ea952d37=0D
https://github.com/fvwmorg/fvwm/commit/3f3ad36421096ef77804fd84fa33=
7338ea952d37=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-10 (Sun, 10 May 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
FScreen: remove debug=0D
=0D
Remove debug, as this is overly verbose.=0D
=0D
=0D
Commit: 56dfadb56925bf0cea327b92a3c4c7b169229125=0D
https://github.com/fvwmorg/fvwm/commit/56dfadb56925bf0cea327b92a3c4=
c7b169229125=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-10 (Sun, 10 May 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/expansion.xml=0D
M fvwm/expand.c=0D
=0D
Log Message:=0D
-----------=0D
expansion: add monitor.X.Y variables=0D
=0D
Consolidate the information about monitors by using "monitors." as a=0D
namespace, and expose information (from xrandr) about the monitors FVWM=0D=
knows about.=0D
=0D
This marks for deprecation some of the older $[screen.X] variables, but=0D=
remain in place for now.=0D
=0D
Parly addresses #59=0D
=0D
=0D
Commit: a60d4029d8166df328ce6019c15d656d5ee68c4e=0D
https://github.com/fvwmorg/fvwm/commit/a60d4029d8166df328ce6019c15d=
656d5ee68c4e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-11 (Mon, 11 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/module_interface.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
BroadcastMonitorList: reorder packet logic=0D
=0D
When a module requests M_CONFIG_INFO for Monitor, recalculate that per=0D=
module, rather than the other way round.=0D
=0D
Should help fix #44=0D
=0D
=0D
Commit: 007cebe1140cf2df17b1e5b9ff152a4f8ae4b611=0D
https://github.com/fvwmorg/fvwm/commit/007cebe1140cf2df17b1e5b9ff15=
2a4f8ae4b611=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-13 (Wed, 13 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/borders.c=0D
M fvwm/events.c=0D
M fvwm/expand.c=0D
M fvwm/virtual.c=0D
=0D
Log Message:=0D
-----------=0D
GCC: fix warnings=0D
=0D
Fix some warnings from GCC.=0D
=0D
=0D
Commit: d9e5b8f7ea32976468d655f7db8f5764f10edcc7=0D
https://github.com/fvwmorg/fvwm/commit/d9e5b8f7ea32976468d655f7db8f=
5764f10edcc7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-17 (Sun, 17 May 2020)=0D
=0D
Changed paths:=0D
A .github/FUNDING.yml=0D
=0D
Log Message:=0D
-----------=0D
Add sponsor=0D
=0D
=0D
Commit: 6927682c65c42278c294f143479ff488437fa53d=0D
https://github.com/fvwmorg/fvwm/commit/6927682c65c42278c294f143479f=
f488437fa53d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-22 (Fri, 22 May 2020)=0D
=0D
Changed paths:=0D
M utils/fvwm-version-str.sh=0D
=0D
Log Message:=0D
-----------=0D
fvwm-version-str: fix release version=0D
=0D
Check for .git directory in CWD, and use released version if not=0D
present, otherwise check the status of the git repository.=0D
=0D
=0D
Commit: b3475d760c969d525e40628231abcc2570a3cab1=0D
https://github.com/fvwmorg/fvwm/commit/b3475d760c969d525e40628231ab=
cc2570a3cab1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-22 (Fri, 22 May 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
randr: assign one output as primary=0D
=0D
RandR doesn't guarantee that there is always one monitor marked as=0D
primary. Certain operations in FVWM expect this, therefore if a primary=0D=
monitor hasn't been set, assign the first monitor found as a default.=0D
=0D
Helps address #78=0D
=0D
=0D
Commit: e253fbcd864f3e5f202632293395d8a00f8776f5=0D
https://github.com/fvwmorg/fvwm/commit/e253fbcd864f3e5f202632293395=
d8a00f8776f5=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-23 (Sat, 23 May 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
=0D
Log Message:=0D
-----------=0D
configure.ac: remove references to FTP=0D
=0D
In FVWM2, the release tarballs used to be stored on a public-facing FTP=0D=
server. This hasn't been true in years, since the switch to Github.=0D
=0D
=0D
Commit: b2a7b335f7f06576eef129232a6fce880da02482=0D
https://github.com/fvwmorg/fvwm/commit/b2a7b335f7f06576eef129232a6f=
ce880da02482=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-23 (Sat, 23 May 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
version: output fvwm3=0D
=0D
When referring to version information, make it clearer this is fvwm3.=0D
=0D
=0D
Commit: ee30219f6d7776b7df15679d4cc8cb68e8f6e2df=0D
https://github.com/fvwmorg/fvwm/commit/ee30219f6d7776b7df15679d4cc8=
cb68e8f6e2df=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-23 (Sat, 23 May 2020)=0D
=0D
Changed paths:=0D
M .gitignore=0D
R doc/fvwm3.ent=0D
=0D
Log Message:=0D
-----------=0D
doc: remove and blacklist docbook *.ent=0D
=0D
Entity files as used by docbook are transient and as such don't need to=0D=
be tracked in git.=0D
=0D
=0D
Commit: 5c63793ae755466b0a258f99b6a8318b647d4e4c=0D
https://github.com/fvwmorg/fvwm/commit/5c63793ae755466b0a258f99b6a8=
318b647d4e4c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-23 (Sat, 23 May 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/fvwm3.c=0D
M modules/FvwmConsole/FvwmConsole.c=0D
M utils/fvwm-version-str.sh=0D
=0D
Log Message:=0D
-----------=0D
configure: resurrect VERSIONINFO=0D
=0D
When embedding the git revision string into the version number of FVWM3,=0D=
don't overwrite VERSION with the git SHA1.=0D
=0D
VERSION is required as the released version so that modules are=0D
maintained in a correct manner, and that version checks for things like=0D=
state files (across FVWM3 reboots) are still honoured correctly.=0D
=0D
=0D
Commit: 938051bc272d49e81924d01fb8eb2f9e24f033b6=0D
https://github.com/fvwmorg/fvwm/commit/938051bc272d49e81924d01fb8eb=
2f9e24f033b6=0D
Author: Vladislav Zavjalov <[email protected]>=0D
Date: 2020-05-24 (Sun, 24 May 2020)=0D
=0D
Changed paths:=0D
M perllib/General/FileSystem.pm=0D
=0D
Log Message:=0D
-----------=0D
remove dependency on Perl4::CoreLibs::getcwd=0D
=0D
=0D
Commit: 3049eb1eee860f97faa78defb8783ce5c6de1e24=0D
https://github.com/fvwmorg/fvwm/commit/3049eb1eee860f97faa78defb878=
3ce5c6de1e24=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-25 (Mon, 25 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
place_window: don't switch desk for transient windows=0D
=0D
When dealing with transient windows, don't switch desks if not=0D
necessary. We don't reference the global desk, so check the transient=0D=
window is on the correct screen first, and ignore all other windows.=0D
=0D
Fixes #95=0D
=0D
=0D
Commit: 193a5c8669fe1f72312c11ab91f0844af706f3d1=0D
https://github.com/fvwmorg/fvwm/commit/193a5c8669fe1f72312c11ab91f0=
844af706f3d1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-25 (Mon, 25 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
=0D
Log Message:=0D
-----------=0D
Capture: force NormalState despite current desk=0D
=0D
When FVWM restarts and captures windows, the window would only have been =
put=0D
in the NormalState if the window's desk was different to the current desk=
.=0D
=0D
This check doesn't need to happen any more, since the desks will likely a=
lmost=0D
always be different when capturing windows (especially if per-monitor mod=
e is=0D
in use).=0D
=0D
Fixes #97=0D
=0D
=0D
Commit: 096bc21fdf95d5ec9c1d9c12de837d2ae28eb6a7=0D
https://github.com/fvwmorg/fvwm/commit/096bc21fdf95d5ec9c1d9c12de83=
7d2ae28eb6a7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-25 (Mon, 25 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
Reproducable builds: remove __DATE__/__TIME__=0D
=0D
So that reproducible builds are possible, remove __DATE__/__TIME__=0D
macros from the code.=0D
=0D
It's not clear who the original author(s) of this patch are, but it's=0D
not originally authored by me (Thomas Adam), but is most definitely a=0D
good idea.=0D
=0D
Fixes #99=0D
=0D
=0D
Commit: 76b8e2ec16e6c6996ce0227554c4c08135637848=0D
https://github.com/fvwmorg/fvwm/commit/76b8e2ec16e6c6996ce0227554c4=
c08135637848=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-25 (Mon, 25 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh.c=0D
=0D
Log Message:=0D
-----------=0D
EWMH: AreaIntersection: fix basestruct calculation=0D
=0D
When performing calculations to work out the base stut intersection,=0D
don't overflow the screen boundaries, by keeping within the limits.=0D
=0D
Fixes #84=0D
=0D
=0D
Commit: 2791dd5db29d01cf45af2329534dc3094e93f16d=0D
https://github.com/fvwmorg/fvwm/commit/2791dd5db29d01cf45af2329534d=
c3094e93f16d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
A libs/asprintf.c=0D
M libs/safemalloc.c=0D
M libs/safemalloc.h=0D
=0D
Log Message:=0D
-----------=0D
compat: add asprintf implementation=0D
=0D
For those systems which don't have asprintf natively, provide a=0D
compatibility implementation.=0D
=0D
=0D
Commit: f20e45b2128150a9f85bb86423dc7fcc39c240fa=0D
https://github.com/fvwmorg/fvwm/commit/f20e45b2128150a9f85bb86423dc=
7fcc39c240fa=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M libs/safemalloc.h=0D
=0D
Log Message:=0D
-----------=0D
safemalloc.h: add include guards=0D
=0D
Don't try and include more headers than is necessary by wrapping them in=0D=
an include guard.=0D
=0D
=0D
Commit: ac9847932194e48b37ff0ed719fc6d313ab8193c=0D
https://github.com/fvwmorg/fvwm/commit/ac9847932194e48b37ff0ed719fc=
6d313ab8193c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M libs/Makefile.am=0D
A libs/log.c=0D
A libs/log.h=0D
=0D
Log Message:=0D
-----------=0D
Add logging capability=0D
=0D
Add log routines (modified from tmux) to be able to log what fvwm3 is=0D
doing in a more structured way than just using fprintf() calls.=0D
=0D
=0D
Commit: 3008435e2f26c2fb34f2b010ce4cc9466323d31b=0D
https://github.com/fvwmorg/fvwm/commit/3008435e2f26c2fb34f2b010ce4c=
c9466323d31b=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/module_interface.c=0D
M fvwm/move_resize.c=0D
M fvwm/virtual.c=0D
M modules/FvwmIconMan/debug.c=0D
=0D
Log Message:=0D
-----------=0D
asprintf: switch to xasprintf=0D
=0D
Move callers of asprintf() to xasprintf().=0D
=0D
=0D
Commit: b3daeca989ab1a021cca3d1f11cd9caf997b278f=0D
https://github.com/fvwmorg/fvwm/commit/b3daeca989ab1a021cca3d1f11cd=
9caf997b278f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
M libs/log.c=0D
M libs/log.h=0D
=0D
Log Message:=0D
-----------=0D
SIGURS2: toggle logging=0D
=0D
Make FVWM3 write or stop writing to a log file, when it receives=0D
SIGUSR2.=0D
=0D
=0D
Commit: d5825b1247f41d402501254350a8dc7c90707642=0D
https://github.com/fvwmorg/fvwm/commit/d5825b1247f41d402501254350a8=
dc7c90707642=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
A contrib/coccinelle/remove_debug.cocci=0D
=0D
Log Message:=0D
-----------=0D
cocci: add remove debug script=0D
=0D
=0D
Commit: 1d39c5b678493c62172ab754958a20941c03b39d=0D
https://github.com/fvwmorg/fvwm/commit/1d39c5b678493c62172ab754958a=
20941c03b39d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/events.c=0D
M fvwm/functions.c=0D
M fvwm/fvwm3.c=0D
M fvwm/icccm2.c=0D
M fvwm/misc.c=0D
M fvwm/module_interface.c=0D
M fvwm/module_list.c=0D
=0D
Log Message:=0D
-----------=0D
debug: remove DBUG macro=0D
=0D
This removes DBUG and associated configur.ac changes.=0D
=0D
This will be replaced with more fuller logging.=0D
=0D
=0D
Commit: 4a639a8648f4f6a2a6273a827f2299c6cccaf30c=0D
https://github.com/fvwmorg/fvwm/commit/4a639a8648f4f6a2a6273a827f22=
99c6cccaf30c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-root.c=0D
M contrib/coccinelle/remove_debug.cocci=0D
M contrib/randr-tool/randr.c=0D
M fvwm/add_window.c=0D
M fvwm/bindings.c=0D
M fvwm/borders.c=0D
M fvwm/builtins.c=0D
M fvwm/colorset.c=0D
M fvwm/conditional.c=0D
M fvwm/cursor.c=0D
M fvwm/events.c=0D
M fvwm/ewmh.c=0D
M fvwm/ewmh_conf.c=0D
M fvwm/ewmh_events.c=0D
M fvwm/ewmh_icons.c=0D
M fvwm/execcontext.c=0D
M fvwm/expand.c=0D
M fvwm/frame.c=0D
M fvwm/functions.c=0D
M fvwm/fvwm3.c=0D
M fvwm/icccm2.c=0D
M fvwm/icons.c=0D
M fvwm/infostore.c=0D
M fvwm/menubindings.c=0D
M fvwm/menucmd.c=0D
M fvwm/menus.c=0D
M fvwm/menustyle.c=0D
M fvwm/misc.c=0D
M fvwm/misc.h=0D
M fvwm/module_interface.c=0D
M fvwm/module_list.c=0D
M fvwm/move_resize.c=0D
M fvwm/placement.c=0D
M fvwm/read.c=0D
M fvwm/schedule.c=0D
M fvwm/session.c=0D
M fvwm/stack.c=0D
M fvwm/style.c=0D
M fvwm/virtual.c=0D
M fvwm/windowlist.c=0D
M fvwm/windowshade.c=0D
M libs/ColorUtils.c=0D
M libs/FGettext.c=0D
M libs/FRender.c=0D
M libs/FScreen.c=0D
M libs/Ficonv.c=0D
M libs/Flocale.c=0D
M libs/FlocaleCharset.c=0D
M libs/Graphics.c=0D
M libs/Picture.c=0D
M libs/PictureImageLoader.c=0D
M libs/PictureUtils.c=0D
M libs/Target.c=0D
M libs/XError.c=0D
M libs/fsm.c=0D
M libs/log.c=0D
M libs/log.h=0D
M libs/safemalloc.c=0D
M modules/FvwmBacker/FvwmBacker.c=0D
M modules/FvwmBacker/root_bits.c=0D
M modules/FvwmButtons/FvwmButtons.c=0D
M modules/FvwmButtons/button.c=0D
M modules/FvwmButtons/draw.c=0D
M modules/FvwmButtons/output.c=0D
M modules/FvwmButtons/parse.c=0D
M modules/FvwmConsole/FvwmConsole.c=0D
M modules/FvwmConsole/FvwmConsoleC.c=0D
M modules/FvwmConsole/getline.c=0D
M modules/FvwmEvent/FvwmEvent.c=0D
M modules/FvwmIconMan/FvwmIconMan.c=0D
M modules/FvwmIconMan/debug.c=0D
M modules/FvwmIconMan/readconfig.c=0D
M modules/FvwmIconMan/x.c=0D
M modules/FvwmIconMan/xmanager.c=0D
M modules/FvwmIdent/FvwmIdent.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmRearrange/FvwmRearrange.c=0D
M modules/FvwmScript/FvwmScript.c=0D
M modules/FvwmScript/Instructions.c=0D
M modules/FvwmScript/Widgets/CheckBox.c=0D
M modules/FvwmScript/Widgets/HScrollBar.c=0D
M modules/FvwmScript/Widgets/ItemDraw.c=0D
M modules/FvwmScript/Widgets/List.c=0D
M modules/FvwmScript/Widgets/Menu.c=0D
M modules/FvwmScript/Widgets/PopupMenu.c=0D
M modules/FvwmScript/Widgets/PushButton.c=0D
M modules/FvwmScript/Widgets/RadioButton.c=0D
M modules/FvwmScript/Widgets/Swallow.c=0D
M modules/FvwmScript/Widgets/TextField.c=0D
M modules/FvwmScript/Widgets/VScrollBar.c=0D
M modules/FvwmScript/Widgets/Widget.c=0D
M modules/FvwmScript/script.c=0D
=0D
Log Message:=0D
-----------=0D
logging: swap callers of stderr to fvwm_debug=0D
=0D
Now that FVWM3 has logging capabilities via SIGUSR2, migrate all=0D
instances of fprintf(stderr, ...) to fvwm_debug(...);=0D
=0D
Although this might make the logfile chatty, it now means we won't miss=0D=
messages otherwise printed to stderr. Some display managers (via=0D
systemd) have started to make it harder to log/find stderr.=0D
=0D
FVWM3 will create a log file in $HOME for the purposes of logging.=0D
=0D
=0D
Commit: 9b0570ee8df867dd7972d7edbcf3e9cfa8e681e7=0D
https://github.com/fvwmorg/fvwm/commit/9b0570ee8df867dd7972d7edbcf3=
e9cfa8e681e7=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
logging: usage should go to stderr=0D
=0D
Don't send fvwm3's usage output to fvwm_debug() -- use stderr.=0D
=0D
=0D
Commit: b2786345bef7083776da3b535af48d06402c83e8=0D
https://github.com/fvwmorg/fvwm/commit/b2786345bef7083776da3b535af4=
8d06402c83e8=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/expand.c=0D
=0D
Log Message:=0D
-----------=0D
expand: portably tokenise string using strsep=0D
=0D
Rather than using sscanf() to try and split a string up to a known=0D
delimiter (period) which is not valid whitespace, instead use strsep()=0D=
to tokenise the string and match on the constituent parts.=0D
=0D
This should avoid segfaults across platforms.=0D
=0D
Fixes #101=0D
=0D
=0D
Commit: f3ef5c32be836c9f6c9b1da9ab90cd161299cf81=0D
https://github.com/fvwmorg/fvwm/commit/f3ef5c32be836c9f6c9b1da9ab90=
cd161299cf81=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm.h=0D
M fvwm/placement.c=0D
M fvwm/screen.h=0D
=0D
Log Message:=0D
-----------=0D
UPDATE_FVWM_SCREEN: respect StartsOnDesk style=0D
=0D
Previously, when StartsOnDesk was used, although the desk was correctly=0D=
set, the desk would never change thereafter, once the window was moved.=0D=
=0D
This was because the UPDATE_FVWM_SCREEN macro assumed it could always=0D
update the window, but never took into account that when moving=0D
monitors, the desk also needed to be changed.=0D
=0D
But this can't blindly happen in all cases, as on initla mapping of the=0D=
window, the UPDATE_FVWM_SCREEN macro would have overriden the=0D
StartsOnDesk style.=0D
=0D
This change introduces a flag to track this as well as reducing the=0D
number of assigments which weren't needed when updating the screen.=0D
Also removed an extraneous assignment.=0D
=0D
Helps #86=0D
=0D
=0D
Commit: a6a9b8581a387ae2a557eefcb54852e34280221d=0D
https://github.com/fvwmorg/fvwm/commit/a6a9b8581a387ae2a557eefcb548=
52e34280221d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-27 (Wed, 27 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/stack.c=0D
=0D
Log Message:=0D
-----------=0D
RaiseLower: ignore windows on other monitors=0D
=0D
When deducing if the windows in the stack ring should be compared=0D
against, only consider those windows on the same monitor as the current=0D=
window.=0D
=0D
Fixes #86=0D
=0D
=0D
Commit: 6866714fcb3b41f8512ef79d3cb903ee96b11d9e=0D
https://github.com/fvwmorg/fvwm/commit/6866714fcb3b41f8512ef79d3cb9=
03ee96b11d9e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-05-28 (Thu, 28 May 2020)=0D
=0D
Changed paths:=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
session: fix version check for used_sm=0D
=0D
When FVWM3 restarts and then tries to recapture windows, it will first=0D=
check that the version of FVWM3 restarting is the same as the version=0D
recorded in the state file.=0D
=0D
Prior to this change, there was an erroneous comma, due to the=0D
reproducible build patch, causing this check to fail.=0D
=0D
=0D
Commit: a684c614b14a5829374c2ff1245277afb4e4c985=0D
https://github.com/fvwmorg/fvwm/commit/a684c614b14a5829374c2ff12452=
77afb4e4c985=0D
Author: Victor Ananjevsky <[email protected]>=0D
Date: 2020-06-01 (Mon, 01 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/ewmh_events.c=0D
=0D
Log Message:=0D
-----------=0D
Windows cannot be moved to desktop/workspace 0 when using facilities of=
thirdparty libraries such as libwnck=0D
=0D
=0D
Commit: 6650d4e7c807a18783c86fd0b3f0ae3b261b1d54=0D
https://github.com/fvwmorg/fvwm/commit/6650d4e7c807a18783c86fd0b3f0=
ae3b261b1d54=0D
Author: Victor Ananjevsky <[email protected]>=0D
Date: 2020-06-01 (Mon, 01 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/Makefile.am=0D
M libs/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
Fix 'dist' target=0D
=0D
=0D
Commit: dd24b3c0178499ceb82fe7b7f94e561148859312=0D
https://github.com/fvwmorg/fvwm/commit/dd24b3c0178499ceb82fe7b7f94e=
561148859312=0D
Author: lgsobalvarro <[email protected]>=0D
Date: 2020-06-02 (Tue, 02 Jun 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
key binding and menu option for dmenu_run=0D
=0D
=0D
Commit: 27b829ea859adc149a7ec6d496a8bab9a7fdd4e8=0D
https://github.com/fvwmorg/fvwm/commit/27b829ea859adc149a7ec6d496a8=
bab9a7fdd4e8=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-02 (Tue, 02 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
verbose: actually open log file=0D
=0D
When passing -v to fvwm3, actually open the log file, rather than just=0D=
setting the log level.=0D
=0D
=0D
Commit: 05fe5aa17e0d54f65aa4dff8ca8cce08d640eb1f=0D
https://github.com/fvwmorg/fvwm/commit/05fe5aa17e0d54f65aa4dff8ca8c=
ce08d640eb1f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-02 (Tue, 02 Jun 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/options.xml=0D
M libs/log.c=0D
=0D
Log Message:=0D
-----------=0D
logging: mention -v and rename log file=0D
=0D
Previously, the log file written to by fvwm3 used to contain the pid in=0D=
the file name. This isn't useful, and since the log file is opened in=0D=
append mode anyway, it makes more sense to remove this.=0D
=0D
Also added a description to the man page.=0D
=0D
Helps with #77=0D
=0D
=0D
Commit: 67232eedaaa18ac019bf5965de40e4686f4284e8=0D
https://github.com/fvwmorg/fvwm/commit/67232eedaaa18ac019bf5965de40=
e4686f4284e8=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-02 (Tue, 02 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
restart: LoadwindowStates: fix NULL dereference=0D
=0D
When restarting fvwm3, a state file is written to disk to record window=0D=
states/positions so that when they're recaptured by fvwm3, the windows=0D=
are as they were before.=0D
=0D
The session code assuems that there is at least one window, which isn't=0D=
necessarily true. This then throws out the reference counting when=0D
reading in information which isn't based on a window -- such as monitor=0D=
information. In such cases, fvwm3 would segfault.=0D
=0D
This is changed to resize the matches list.=0D
=0D
=0D
Commit: 03d0205779f951a229aa497dafd5a3d673ca12fc=0D
https://github.com/fvwmorg/fvwm/commit/03d0205779f951a229aa497dafd5=
a3d673ca12fc=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-03 (Wed, 03 Jun 2020)=0D
=0D
Changed paths:=0D
A .github/issue_label_bot.yaml=0D
=0D
Log Message:=0D
-----------=0D
issue_bot: add YAML config file=0D
=0D
Teach issue bot about the labels FVWM3 uses.=0D
=0D
=0D
Commit: d23ba82834e3f8242eaa060b6f57e42d0c491d5d=0D
https://github.com/fvwmorg/fvwm/commit/d23ba82834e3f8242eaa060b6f57=
e42d0c491d5d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-03 (Wed, 03 Jun 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
=0D
Log Message:=0D
-----------=0D
GCC-10: enable -fcommon for linking=0D
=0D
With GCC 10 -fno-common is enabled by default[0] which causes linking=0D
problems that might look like this:=0D
=0D
/usr/bin/ld: read.o:/home/n6tadam/projects/fvwm/fvwm3/fvwm/../libs/FScree=
n.h:169:=0D
multiple definition of `randr_event';=0D
menus.o:/home/n6tadam/projects/fvwm/fvwm3/fvwm/../libs/FScreen.h:169:=0D
first defined here=0D
=0D
To fix this properly, extern declarations will be required. But for=0D
now, just disable this.=0D
=0D
Helps #119=0D
=0D
[0] https://gcc.gnu.org/gcc-10/porting_to.html#common=0D
=0D
=0D
Commit: 8562844ef9a0935ea6f4fbb23e30c777e89115f0=0D
https://github.com/fvwmorg/fvwm/commit/8562844ef9a0935ea6f4fbb23e30=
c777e89115f0=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-04 (Thu, 04 Jun 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M fvwm/virtual.c=0D
M fvwm/virtual.h=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
GCC-10: default to -fno-common by default=0D
=0D
GCC-10+ has switched -fno-common on by default. Previously, this was=0D
causing compilation failures where the .DATA blocks are now used, which=0D=
means extern variables need declaring outside of .h files.=0D
=0D
This change makes those adjustments.=0D
=0D
Fixes #119=0D
=0D
=0D
Commit: 8bc06ddef6fdb9ed5134911f3a21777507261322=0D
https://github.com/fvwmorg/fvwm/commit/8bc06ddef6fdb9ed5134911f3a21=
777507261322=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-05 (Fri, 05 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
setup_window_placement: initialise screen correctly=0D
=0D
When setting up the window, set the screen flags for the specific=0D
screen, if StartsOnScreen is used. The screen is only set up once here,=0D=
before the information is set to the placement algorithms.=0D
=0D
Prior to this change, the screen wasn't being expanded, and was always=0D=
returning a blank screen. Furthermore, this was throwing off other=0D
calculations.=0D
=0D
Fixes #115=0D
=0D
=0D
Commit: 8e7983b211314b536455f880e2237862134807c5=0D
https://github.com/fvwmorg/fvwm/commit/8e7983b211314b536455f880e223=
7862134807c5=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-06 (Sat, 06 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M fvwm/module_interface.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
=0D
Log Message:=0D
-----------=0D
RandR: track monitor enable/disable/change events=0D
=0D
In order for FvwmEvent to know when certain RandR events have occured,=0D=
change the way RandR events are tracked, and set flags on the monitor to=0D=
indicate what RandR changes have happened.=0D
=0D
Only debug logging tracks this, the changes for FvwmEvent will come=0D
later.=0D
=0D
=0D
Commit: 374cf0f58f34951f6f8c28a3da9520f4690d0e57=0D
https://github.com/fvwmorg/fvwm/commit/374cf0f58f34951f6f8c28a3da95=
20f4690d0e57=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-06 (Sat, 06 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/Module.h=0D
M modules/FvwmEvent/FvwmEvent.1.in=0D
M modules/FvwmEvent/FvwmEvent.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmEvent: listen for RandR events=0D
=0D
This adds the work necessary to make FvwmEvent listen for RandR events.=0D=
Three events are supported:=0D
=0D
* monitor_enabled -- when a monitor is "plugged" in, and active;=0D
* monitor_disabled -- when a monitor is "unplugged" and deactivated;=0D
* monitor_changed -- when an enabled monitor changes resolution/rotation=0D=
=0D
An "emit" flag is used to track events, separate from the on-going state=0D=
of RandR itself.=0D
=0D
Fixes #26=0D
=0D
=0D
Commit: c5712dd0d1d516909b87c085000e019b80da95d0=0D
https://github.com/fvwmorg/fvwm/commit/c5712dd0d1d516909b87c085000e=
019b80da95d0=0D
Author: Hegel3DReloaded <[email protected]>=0D
Date: 2020-06-07 (Sun, 07 Jun 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/environment.xml=0D
M fvwm/fvwm3.c=0D
M libs/Makefile.am=0D
A libs/getpwuid.c=0D
A libs/getpwuid.h=0D
M libs/log.c=0D
M libs/log.h=0D
=0D
Log Message:=0D
-----------=0D
Add FVWM3_LOGDIR envvar for logging to different file=0D
=0D
=0D
Commit: ee5eae863a578c7fb9bd2d971a7849cf026cec56=0D
https://github.com/fvwmorg/fvwm/commit/ee5eae863a578c7fb9bd2d971a78=
49cf026cec56=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-07 (Sun, 07 Jun 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
FindScreenOfXY: remove debug if no monitor found=0D
=0D
It's not likely that we're able to map a coordinate to a screen.=0D
However, sometimes this can happen early on in FVWM's start up.=0D
=0D
This error is misleading -- and instead we should remove it.=0D
=0D
Fixes #93=0D
=0D
=0D
Commit: 6e646e6201051d19dea5fa8e985fcaf884f0d94d=0D
https://github.com/fvwmorg/fvwm/commit/6e646e6201051d19dea5fa8e985f=
caf884f0d94d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-09 (Tue, 09 Jun 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
XRandR: make core dependency=0D
=0D
RandR is sufficiently ubiquitous across Linux distributions and BSDs=0D
that trying to maintain compatibility without it is not worth the=0D
effort.=0D
=0D
Although this might upset some people with very old SPARC machines or=0D
ailing VAX machines, other even older WMs (FVWM1x/OLVWM) are available.=0D=
=0D
=0D
Commit: 1b1279fee319d6809c55e1483d273a985f0e97e4=0D
https://github.com/fvwmorg/fvwm/commit/1b1279fee319d6809c55e1483d27=
3a985f0e97e4=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-09 (Tue, 09 Jun 2020)=0D
=0D
Changed paths:=0D
M dev-docs/INSTALL.md=0D
=0D
Log Message:=0D
-----------=0D
INSTALL: mention dependencies=0D
=0D
Update the documentation for core/optional dependencies, now that RandR=0D=
is mandatory.=0D
=0D
=0D
Commit: 6880de7777738bf38a3048596870822c122305d3=0D
https://github.com/fvwmorg/fvwm/commit/6880de7777738bf38a3048596870=
822c122305d3=0D
Author: Jaimos Skriletz <[email protected]>=0D
Date: 2020-06-15 (Mon, 15 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/x_pager.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmPager: bound windows to monitor viewport=0D
=0D
When FvwmPager is in "per-monitor" mode (that is, been configured with=0D=
"*FvwmPager: Monitor <name>"), it is only ever useful to show the=0D
windows which are on that monitor.=0D
=0D
To achieve this, we therfore need to translate the windows's coordinates=0D=
to the bounding "view" the monitor the window is on has (that is, its=0D
own width/height).=0D
=0D
Translate the window's position (which is relative to the entire XServer=0D=
display) to the appropriate monitor, and keep tracking where it is.=0D
=0D
This rewrites the CalcGeom() function which previously used a "mirroring"=
=0D
technique to reflect the bounds of the window in the pager.=0D
=0D
Helps #44=0D
=0D
=0D
Commit: 3349250407c5d04dfe4ef8f109bac51751e5c48b=0D
https://github.com/fvwmorg/fvwm/commit/3349250407c5d04dfe4ef8f109ba=
c51751e5c48b=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-15 (Mon, 15 Jun 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M modules/FvwmPager/FvwmPager.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmPager: disable WORRY_ABOUT_MISSED_XEVENTS=0D
=0D
Don't kill FvwmPager if there's too many missed XEvents. These are=0D
weeded out during scrolling, and hence the original check is no longer=0D=
required.=0D
=0D
=0D
Commit: 6c0c06163c5f6accee91f8c7b6ab8f3728c05e58=0D
https://github.com/fvwmorg/fvwm/commit/6c0c06163c5f6accee91f8c7b6ab=
8f3728c05e58=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-15 (Mon, 15 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.1.in=0D
=0D
Log Message:=0D
-----------=0D
FvwmPager.1: remove COPYRIGHT section=0D
=0D
The copyright licence on FVWM is GPL, and as such Robert Nation has=0D
already given his blessing for that. Hence, this notice doesn't need to=0D=
be in the man page. Similar messages in comments in code elsewhere have=0D=
already been removed.=0D
=0D
=0D
Commit: d24dfb56c521d7e9465a3ee70cd587a824c85fd1=0D
https://github.com/fvwmorg/fvwm/commit/d24dfb56c521d7e9465a3ee70cd5=
87a824c85fd1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-15 (Mon, 15 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.1.in=0D
=0D
Log Message:=0D
-----------=0D
FvwmPager.1: add 'Monitor' config option=0D
=0D
Describe what "*FvwmPager: Monitor xxx" does.=0D
=0D
=0D
Commit: aade0af0426002221542cb6b4fccf89266d7eff3=0D
https://github.com/fvwmorg/fvwm/commit/aade0af0426002221542cb6b4fcc=
f89266d7eff3=0D
Author: lgsobalvarro <[email protected]>=0D
Date: 2020-06-24 (Wed, 24 Jun 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
New colorset for cfg=0D
=0D
=0D
Commit: 8b06163f2106a709388d320657b44f1265b36b05=0D
https://github.com/fvwmorg/fvwm/commit/8b06163f2106a709388d320657b4=
4f1265b36b05=0D
Author: Jaimos Skriletz <[email protected]>=0D
Date: 2020-06-24 (Wed, 24 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmIconMan/xmanager.c=0D
=0D
Log Message:=0D
-----------=0D
Fixes issue with FvwmIconMan and Colorsets.=0D
=0D
FvwmIconMan would not apply the background colorset=0D
to blank buttons in certain situations.=0D
=0D
=0D
Commit: 0e6a2249a02ea4d37a0d3e7bcc147e0f9c0f78b6=0D
https://github.com/fvwmorg/fvwm/commit/0e6a2249a02ea4d37a0d3e7bcc14=
7e0f9c0f78b6=0D
Author: lgsobalvarro <[email protected]>=0D
Date: 2020-06-24 (Wed, 24 Jun 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
Update config=0D
=0D
=0D
Commit: ecfed511d353c6210297aabbd6ddf859ad137411=0D
https://github.com/fvwmorg/fvwm/commit/ecfed511d353c6210297aabbd6dd=
f859ad137411=0D
Author: lgsobalvarro <[email protected]>=0D
Date: 2020-06-24 (Wed, 24 Jun 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
Added $infostore for dmenu=0D
=0D
=0D
Commit: a42f6a950596d6c3c3076814bb0cfa5f6ada9a11=0D
https://github.com/fvwmorg/fvwm/commit/a42f6a950596d6c3c3076814bb0c=
fa5f6ada9a11=0D
Author: Jaimos Skriletz <[email protected]>=0D
Date: 2020-06-26 (Fri, 26 Jun 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/expansion.xml=0D
M fvwm/expand.c=0D
M libs/ColorUtils.c=0D
M libs/ColorUtils.h=0D
=0D
Log Message:=0D
-----------=0D
Colorset variable expansion features.=0D
=0D
* Added appending .lighten<p> and .darken<p> to a colorset=0D
variable expansion, such as $[fg.cs<n>.lighten<p>]=0D
or $[shadow.cs<n>.darken<p>], that will lighten or darken=0D
the color by percentage p before outputing the color string.=0D
* Added appending .hash to the end of the colorset variable=0D
expansion to output the color as a hash, "#rrggbb", instead=0D
of the color form "rgb:rrrr/gggg/bbbb". Examples:=0D
$[bg.cs10.hash] or $[fgsh.cs5.darken20.hash].=0D
* Added missing $[fgsh.cs<n>] description to the manpage.=0D
=0D
=0D
Commit: a85116f0147af7912a0caf5e3295678e53ea10c3=0D
https://github.com/fvwmorg/fvwm/commit/a85116f0147af7912a0caf5e3295=
678e53ea10c3=0D
Author: Jaimos <[email protected]>=0D
Date: 2020-06-26 (Fri, 26 Jun 2020)=0D
=0D
Changed paths:=0D
M doc/fvwm/expansion.xml=0D
M fvwm/expand.c=0D
=0D
Log Message:=0D
-----------=0D
Apply suggestions from code review=0D
=0D
Co-authored-by: Thomas Adam <[email protected]>=0D
=0D
=0D
Commit: 8ba1ac7009f45d16a08ec1eedb9cdd61615fb789=0D
https://github.com/fvwmorg/fvwm/commit/8ba1ac7009f45d16a08ec1eedb9c=
dd61615fb789=0D
Author: Jaimos Skriletz <[email protected]>=0D
Date: 2020-06-26 (Fri, 26 Jun 2020)=0D
=0D
Changed paths:=0D
M default-config/config=0D
A default-config/images/icons/info.png=0D
A default-config/images/icons/win/bottom.png=0D
A default-config/images/icons/win/close.png=0D
A default-config/images/icons/win/destroy.png=0D
A default-config/images/icons/win/done.png=0D
A default-config/images/icons/win/iconify.png=0D
A default-config/images/icons/win/lower.png=0D
A default-config/images/icons/win/max.png=0D
A default-config/images/icons/win/move.png=0D
A default-config/images/icons/win/raise.png=0D
A default-config/images/icons/win/resize.png=0D
A default-config/images/icons/win/sendto.png=0D
A default-config/images/icons/win/shade.png=0D
A default-config/images/icons/win/stays.png=0D
A default-config/images/icons/win/sticky.png=0D
A default-config/images/icons/win/title.png=0D
A default-config/images/icons/win/top.png=0D
=0D
Log Message:=0D
-----------=0D
Add icons to the WindowOpsLong menus for default-config.=0D
=0D
=0D
Commit: 61b443a3f9aad903efaaed773c95222475694144=0D
https://github.com/fvwmorg/fvwm/commit/61b443a3f9aad903efaaed773c95=
222475694144=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
M .github/workflows/ccpp.yml=0D
A Dockerfile=0D
=0D
Log Message:=0D
-----------=0D
Github Actions: switch to using Docker=0D
=0D
Many of the free-to-use CI systems work great, but lack environments=0D
which are up to date. Github Actions is no exception, alas.=0D
=0D
In order to ensure that newer version of libraries can be accessed, use=0D=
a Docker environment. The one Github Actions uses is stored on=0D
fvwmorg's Package site, which has pre-existing libraries installed.=0D
=0D
Any updates to dependencies will mean that the fvwm3-build:latest docker=0D=
environment will need updating.=0D
=0D
=0D
Commit: acac310d7071fc14600923e0a8a347077b61963d=0D
https://github.com/fvwmorg/fvwm/commit/acac310d7071fc14600923e0a8a3=
47077b61963d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
A .disabled-travis.yml=0D
R .travis.yml=0D
M dev-docs/DEVELOPERS.md=0D
M dev-docs/INSTALL.md=0D
=0D
Log Message:=0D
-----------=0D
CI: disable travis-ci=0D
=0D
Now that Github Actions works well enough, don't depend on travis-ci for=0D=
fvwm3 which has always been a PITA to get the correct environments=0D
going.=0D
=0D
travis-ci does use Docker, so this might get resurrected in the future.=0D=
=0D
=0D
Commit: 7cc547a20f130ff9df7da3adaf6c2d65169826f1=0D
https://github.com/fvwmorg/fvwm/commit/7cc547a20f130ff9df7da3adaf6c=
2d65169826f1=0D
Author: The Codacy Badger <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
Add Codacy badge=0D
=0D
=0D
Commit: cbeb2439a8f9893c8767f398edab954330005d3e=0D
https://github.com/fvwmorg/fvwm/commit/cbeb2439a8f9893c8767f398edab=
954330005d3e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
M README.md=0D
=0D
Log Message:=0D
-----------=0D
Github shields: switch to Actions=0D
=0D
Migrate the CI shield from Travis-CI to Github Actions.=0D
=0D
=0D
Commit: 0a269c6412b8dc653abba9088cd20634ed32eac2=0D
https://github.com/fvwmorg/fvwm/commit/0a269c6412b8dc653abba9088cd2=
0634ed32eac2=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
M .github/workflows/ccpp.yml=0D
M Dockerfile=0D
=0D
Log Message:=0D
-----------=0D
CI: switch to using image on Docker hub=0D
=0D
Until such time that Github Actions allow for pulling from public Docker=0D=
images without credentials, move this to Docker Hub.=0D
=0D
This sucks.=0D
=0D
=0D
Commit: cee20aa6fd5e552bee881969fe1f21717d43b3bc=0D
https://github.com/fvwmorg/fvwm/commit/cee20aa6fd5e552bee881969fe1f=
21717d43b3bc=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-06-29 (Mon, 29 Jun 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
M libs/FScreen.c=0D
M libs/FScreen.h=0D
M libs/Module.h=0D
M modules/FvwmPager/FvwmPager.c=0D
=0D
Log Message:=0D
-----------=0D
monitor: track focus event separately=0D
=0D
When modules learned of the ability to send monitor information, this=0D
was previously sent on all window focus events, as the FVWM modules=0D
required this to reset which monitor had the focus.=0D
=0D
This is not ideal with other modules which end up consuming this=0D
information when they might not care about monitor information at all.=0D=
=0D
Instead, remove BroadcastMonitor() from FocusIn events and set FvwmPager=0D=
to be a listener of MX_MONITOR_FOCUS.=0D
=0D
=0D
Commit: c9a4e8c09a10508bae9a42ad8d5b3d9b27dd0422=0D
https://github.com/fvwmorg/fvwm/commit/c9a4e8c09a10508bae9a42ad8d5b=
3d9b27dd0422=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-06-30 (Tue, 30 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.c=0D
=0D
Log Message:=0D
-----------=0D
if monitor name happens to get updated in ParseOptions, the rest of con=
fig file is skipped.=0D
=0D
=0D
Commit: 9b9d0da2c72bb8ffb29978e75a5dee13fcac950b=0D
https://github.com/fvwmorg/fvwm/commit/9b9d0da2c72bb8ffb29978e75a5d=
ee13fcac950b=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-06-30 (Tue, 30 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
added helper function extract_monitor_config to extract monitor params =
from string=0D
=0D
=0D
Commit: 427902531891c33204fdc82f7f0e8b78ad5e69b5=0D
https://github.com/fvwmorg/fvwm/commit/427902531891c33204fdc82f7f0e=
8b78ad5e69b5=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-06-30 (Tue, 30 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.c=0D
=0D
Log Message:=0D
-----------=0D
Update modules/FvwmPager/FvwmPager.c=0D
=0D
Co-authored-by: Thomas Adam <[email protected]>=0D
=0D
=0D
Commit: 086e1ac9d7f4ca555ced542201c8089066b55a3c=0D
https://github.com/fvwmorg/fvwm/commit/086e1ac9d7f4ca555ced542201c8=
089066b55a3c=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-06-30 (Tue, 30 Jun 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
fixed indentation and style..=0D
=0D
=0D
Commit: 134c777f0915aebf37e710b239096f615b88fe95=0D
https://github.com/fvwmorg/fvwm/commit/134c777f0915aebf37e710b23909=
6f615b88fe95=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-02 (Thu, 02 Jul 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
screen_info_new: use fxcalloc=0D
=0D
Fvwm3 has been using a wrapper around calloc() for some time to catch=0D
either a NULL condition or the size being < 0. Use it.=0D
=0D
=0D
Commit: ea5026cb53475bbd9346304621f23af79fba86e1=0D
https://github.com/fvwmorg/fvwm/commit/ea5026cb53475bbd9346304621f2=
3af79fba86e1=0D
Author: Kleber <[email protected]>=0D
Date: 2020-07-02 (Thu, 02 Jul 2020)=0D
=0D
Changed paths:=0D
M contrib/randr-tool/randr.c=0D
M fvwm/icons.c=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
replace calloc by fxcalloc=0D
=0D
=0D
Commit: 98ff030910159d327a015257bd8a769904134bb6=0D
https://github.com/fvwmorg/fvwm/commit/98ff030910159d327a015257bd8a=
769904134bb6=0D
Author: Kleber <[email protected]>=0D
Date: 2020-07-02 (Thu, 02 Jul 2020)=0D
=0D
Changed paths:=0D
M libs/FScreen.c=0D
=0D
Log Message:=0D
-----------=0D
removing unnecessary comment=0D
=0D
=0D
Commit: d35bb50a9945f7be8537cfb0c4d772a1475bcd25=0D
https://github.com/fvwmorg/fvwm/commit/d35bb50a9945f7be8537cfb0c4d7=
72a1475bcd25=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-03 (Fri, 03 Jul 2020)=0D
=0D
Changed paths:=0D
M dev-docs/DEVELOPERS.md=0D
=0D
Log Message:=0D
-----------=0D
Update DEVELOPERS.md=0D
=0D
Explicitly use fvwm3, rather than fvwm.=0D
=0D
=0D
Commit: 106566d5eadae3bac615f0d9639ed304c04a1d21=0D
https://github.com/fvwmorg/fvwm/commit/106566d5eadae3bac615f0d9639e=
d304c04a1d21=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-03 (Fri, 03 Jul 2020)=0D
=0D
Changed paths:=0D
M dev-docs/DEVELOPERS.md=0D
=0D
Log Message:=0D
-----------=0D
Additional FVWM3 references=0D
=0D
Be explicit about fvwm3, and mention how to use topic branches for PRs.=0D=
=0D
=0D
Commit: c86b79473bb81b80fb96a77684ff273d87e42247=0D
https://github.com/fvwmorg/fvwm/commit/c86b79473bb81b80fb96a77684ff=
273d87e42247=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-07-05 (Sun, 05 Jul 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
better checks for icon size=0D
=0D
=0D
Commit: ac9a8bfda56f8e69979b12c4b70ebe5ec3ad129b=0D
https://github.com/fvwmorg/fvwm/commit/ac9a8bfda56f8e69979b12c4b70e=
be5ec3ad129b=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-07-05 (Sun, 05 Jul 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
uses PIL or ImageMagick to scale icons=0D
=0D
=0D
Commit: 0e7611968938490898ea4b30b1bbed1ea3c1407a=0D
https://github.com/fvwmorg/fvwm/commit/0e7611968938490898ea4b30b1bb=
ed1ea3c1407a=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-07-05 (Sun, 05 Jul 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
fix typo=0D
=0D
Co-authored-by: Thomas Adam <[email protected]>=0D
=0D
=0D
Commit: 48dd50909b97170d517aa02c735cc86881564cb6=0D
https://github.com/fvwmorg/fvwm/commit/48dd50909b97170d517aa02c735c=
c86881564cb6=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-08 (Wed, 08 Jul 2020)=0D
=0D
Changed paths:=0D
M .disabled-travis.yml=0D
M .github/workflows/ccpp.yml=0D
M .gitignore=0D
M configure.ac=0D
M dev-docs/INSTALL.md=0D
M libs/Makefile.am=0D
A modules/FvwmMFL/FvwmMFL.1.in=0D
A modules/FvwmMFL/FvwmMFL.c=0D
A modules/FvwmMFL/Makefile.am=0D
A modules/FvwmMFL/test_fmd.pl=0D
M modules/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
FvwmMFL: Fvwm Module Front Loader=0D
=0D
This introduces a new module which exposes internal Fvwm events as JSON=0D=
objects. This module is intended to provide information from Fvwm in a=0D=
language-agnostic way, allowing Fvwm modules to be written in any=0D
language.=0D
=0D
=0D
Commit: 1a4fac91a2aae9c9424fa12fc9997fd893171ee9=0D
https://github.com/fvwmorg/fvwm/commit/1a4fac91a2aae9c9424fa12fc999=
7fd893171ee9=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-11 (Sat, 11 Jul 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
M fvwm/events.c=0D
M modules/FvwmPager/FvwmPager.c=0D
M modules/FvwmPager/FvwmPager.h=0D
=0D
Log Message:=0D
-----------=0D
Fix compiler warnings=0D
=0D
Fix some trivial warnings.=0D
=0D
=0D
Commit: 0dad2ce1c065c0c8f1a9c0e8f7997f714ec42b6a=0D
https://github.com/fvwmorg/fvwm/commit/0dad2ce1c065c0c8f1a9c0e8f799=
7f714ec42b6a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-12 (Sun, 12 Jul 2020)=0D
=0D
Changed paths:=0D
M dev-docs/INSTALL.md=0D
=0D
Log Message:=0D
-----------=0D
INSTALL: add version to libbson=0D
=0D
=0D
Commit: 7b5cabfeae711474fc4c2eec1f6835cc0d25b7b6=0D
https://github.com/fvwmorg/fvwm/commit/7b5cabfeae711474fc4c2eec1f68=
35cc0d25b7b6=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-21 (Tue, 21 Jul 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
M libs/log.c=0D
M libs/log.h=0D
=0D
Log Message:=0D
-----------=0D
log: write log relative to FVWM_USERDIR=0D
=0D
When Fvwm3 is writing out its log files, ensure that the logs are=0D
written out relative to FVWM_USERDIR by default.=0D
=0D
This can be overwritten by FVWM3_LOGFILE.=0D
=0D
=0D
Commit: aefd22b33f2ffb3d8041b8f2297c01b27108f02a=0D
https://github.com/fvwmorg/fvwm/commit/aefd22b33f2ffb3d8041b8f2297c=
01b27108f02a=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-07-21 (Tue, 21 Jul 2020)=0D
=0D
Changed paths:=0D
M doc/commands/PrintInfo.xml=0D
M doc/fvwm/description.xml=0D
M doc/fvwm/environment.xml=0D
M doc/fvwm/ewmh.xml=0D
M doc/fvwm/options.xml=0D
M doc/fvwm/synopsis.xml=0D
M doc/index.html=0D
=0D
Log Message:=0D
-----------=0D
update documentatation for PrintInfo : it now writes to ~/fvwm3-output.=
log instead of stderr.=0D
=0D
=0D
Commit: fa35f6efa9ebf2b683c7201bb1a8f4d3533c2380=0D
https://github.com/fvwmorg/fvwm/commit/fa35f6efa9ebf2b683c7201bb1a8=
f4d3533c2380=0D
Author: d-e-e-p <[email protected]>=0D
Date: 2020-07-21 (Tue, 21 Jul 2020)=0D
=0D
Changed paths:=0D
M doc/commands/PrintInfo.xml=0D
M doc/fvwm/options.xml=0D
=0D
Log Message:=0D
-----------=0D
- fixed link to manpage in index.html=0D
- added documentation on using SIGUSR1/SIGUSR2 to manpage=0D
- cleanup of intro to fvwm in manpage=0D
- add pointers to override default config/log files using env vars=0D
- update PrintInfo doc to explain how to see output from command=0D
- move default debug log file from $HOME to $FVWM_USERDIR (patch by=0D
ThomasAdam)=0D
=0D
=0D
Commit: 3fc858d19544be35b72116b00920bdb7fd6dfea6=0D
https://github.com/fvwmorg/fvwm/commit/3fc858d19544be35b72116b00920=
bdb7fd6dfea6=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-07-24 (Fri, 24 Jul 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
associate wmclass/wmname and the miniicon using desktop entries=0D
=0D
=0D
Commit: 35e24b2c8e93ac49f70e1313a136539960185837=0D
https://github.com/fvwmorg/fvwm/commit/35e24b2c8e93ac49f70e1313a136=
539960185837=0D
Author: Oleg Telerman <[email protected]>=0D
Date: 2020-07-24 (Fri, 24 Jul 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
=0D
Log Message:=0D
-----------=0D
fix typo in error message on libbson not found=0D
=0D
=0D
Commit: 90d8ee140917d0937eaa7fc8b56f8359adc9128a=0D
https://github.com/fvwmorg/fvwm/commit/90d8ee140917d0937eaa7fc8b56f=
8359adc9128a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-24 (Fri, 24 Jul 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-config.in=0D
M configure.ac=0D
M dev-docs/COMMANDS=0D
M dev-docs/PARSING.md=0D
M doc/allCommands.html=0D
M doc/commands/CursorStyle.xml=0D
M doc/commands/PrintInfo.xml=0D
R doc/commands/Stroke.xml=0D
R doc/commands/StrokeFunc.xml=0D
M doc/fvwm/bindings.xml=0D
M doc/fvwm/commands.xml=0D
M doc/fvwm/ewmh.xml=0D
M doc/fvwm/options.xml=0D
M doc/groupedCommands.html=0D
M doc/util/cmds.txt=0D
M fvwm/Makefile.am=0D
M fvwm/bindings.c=0D
M fvwm/builtins.c=0D
M fvwm/commands.h=0D
M fvwm/eventhandler.h=0D
M fvwm/eventmask.h=0D
M fvwm/events.c=0D
M fvwm/functable.c=0D
M fvwm/fvwm3.c=0D
M fvwm/menubindings.c=0D
M fvwm/module_list.c=0D
M libs/Bindings.c=0D
M libs/Bindings.h=0D
M modules/FvwmScript/FvwmScript.c=0D
M modules/FvwmScript/Instructions.c=0D
M perllib/FVWM/Commands.pm=0D
=0D
Log Message:=0D
-----------=0D
Remove support for libstroke=0D
=0D
Although mouse gestures via libstroke were a nice experiment, its use=0D
never really took off, in all but a few configurations.=0D
=0D
Given the library itself is no longer maintained, some Linux=0D
distributions have stopped shipping it altogether. Although FVWM3 can=0D=
be told to not compile with libstroke support, removing the code=0D
altogether makes sense.=0D
=0D
Fixes #165=0D
=0D
=0D
Commit: 4a30c4fbdfd258012dbf612f005485b2e2f2bd9f=0D
https://github.com/fvwmorg/fvwm/commit/4a30c4fbdfd258012dbf612f0054=
85b2e2f2bd9f=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-26 (Sun, 26 Jul 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmMFL: start by default=0D
=0D
Despite the functionality of this being a module, try and start FvwmMFL=0D=
by default, and not have the user add it to their configs. This gives a=0D=
greater chance of external modules using FvwmMFL of working out of the=0D=
box.=0D
=0D
=0D
Commit: c57e7ecf9ab62d36def8001f9c1da33d2a00ad31=0D
https://github.com/fvwmorg/fvwm/commit/c57e7ecf9ab62d36def8001f9c1d=
a33d2a00ad31=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-26 (Sun, 26 Jul 2020)=0D
=0D
Changed paths:=0D
M fvwm/bindings.c=0D
M libs/Bindings.c=0D
=0D
Log Message:=0D
-----------=0D
libstroke: fix botched bindings=0D
=0D
When support for libstroke was removed, some of the logic was=0D
incorrectly applied for mouse bindings. Fix this by not predicating=0D
bindings for mouse button 0.=0D
=0D
=0D
Commit: 9cb189d82e0319c0c7eeeb9b5d91a6976a9f881d=0D
https://github.com/fvwmorg/fvwm/commit/9cb189d82e0319c0c7eeeb9b5d91=
a6976a9f881d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-07-26 (Sun, 26 Jul 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmMFL/FvwmMFL.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmMFL: add newline to end out write buffer=0D
=0D
When sending responses to clients, append an additional newline=0D
character so that the message can be unbuffered if required. This stops=0D=
the need for clients to do this.=0D
=0D
=0D
Commit: 8249c39f636219148e32f1ea6b0e5d9abf1aeaa2=0D
https://github.com/fvwmorg/fvwm/commit/8249c39f636219148e32f1ea6b0e=
5d9abf1aeaa2=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-08-05 (Wed, 05 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
fix crash in the menu script; escape menuitem text=0D
=0D
=0D
Commit: 08f755a4e62a007d7ee68f4351111fad36b7c50d=0D
https://github.com/fvwmorg/fvwm/commit/08f755a4e62a007d7ee68f435111=
1fad36b7c50d=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-08-05 (Wed, 05 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
catch the exception if conversion fails=0D
=0D
=0D
Commit: 601dc21a0ab812023ee23718bd94dda6e5c99785=0D
https://github.com/fvwmorg/fvwm/commit/601dc21a0ab812023ee23718bd94=
dda6e5c99785=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-08-12 (Wed, 12 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/fvwm-menu-desktop.in=0D
=0D
Log Message:=0D
-----------=0D
catch when _do_check() fails=0D
=0D
=0D
Commit: 6e65b85d127de9b18022c8073974c2f3745b14a1=0D
https://github.com/fvwmorg/fvwm/commit/6e65b85d127de9b18022c8073974=
c2f3745b14a1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-13 (Thu, 13 Aug 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
A modules/FvwmForm/Changes=0D
A modules/FvwmForm/FvwmForm-Capture=0D
A modules/FvwmForm/FvwmForm-Desktop=0D
A modules/FvwmForm/FvwmForm-Form=0D
A modules/FvwmForm/FvwmForm-QuitVerify=0D
A modules/FvwmForm/FvwmForm-Rlogin=0D
A modules/FvwmForm/FvwmForm-RootCursor=0D
A modules/FvwmForm/FvwmForm-RootCursor.pl=0D
A modules/FvwmForm/FvwmForm-Talk=0D
A modules/FvwmForm/FvwmForm-TalkHelp=0D
A modules/FvwmForm/FvwmForm-XDGMenuHelp=0D
A modules/FvwmForm/FvwmForm-XDGOptionsHelp=0D
A modules/FvwmForm/FvwmForm.1.in=0D
A modules/FvwmForm/FvwmForm.c=0D
A modules/FvwmForm/FvwmForm.h=0D
A modules/FvwmForm/Makefile.am=0D
A modules/FvwmForm/ParseCommand.c=0D
A modules/FvwmForm/ReadXServer.c=0D
M modules/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
FvwmForm: resurrect from retirement=0D
=0D
A few years ago, in conversation with various people on IRC and some via=0D=
email, it was clear then that FvwmForm could be deprecated in favour of=0D=
FvwmScript because that was the module which was being more widely used,=0D=
and had support for widgets which FvwmForm did not.=0D
=0D
However, in speaking to Dan Espen (the primary author of FvwmForm), he=0D=
always had the idea to augment FvwmForm with better features than=0D
FvwmScipt. Indeed, Dan makes a good point that FvwmScript's comments=0D
are in French which doesn't make it easier to non-French speakers to=0D
understand them, *and* follow the code at the same time.=0D
=0D
The default assumption in deprecating FvwmForm for FvwmScript -- because=0D=
FvwmScript was deemed a superset -- doesn't hold try any more. If=0D
anything, it's more likely to go the other way; removing FvwmScript for=0D=
FvwmForm.=0D
=0D
Until we work out what do to about this, we'll need to reinstate=0D
FvwmForm in order to start using it.=0D
=0D
There's a few tweaks to the code to make it compile against newer APIs=0D=
introduced since FvwmForm was deprecated.=0D
=0D
Thanks to Dan Espen for his patience!=0D
=0D
=0D
Commit: 873f5c9af9cb05582fb13a44d5d3c49062ee0d35=0D
https://github.com/fvwmorg/fvwm/commit/873f5c9af9cb05582fb13a44d5d3=
c49062ee0d35=0D
Author: Jean Philippe EIMER <[email protected]>=0D
Date: 2020-08-16 (Sun, 16 Aug 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmScript/FvwmScript.c=0D
M modules/FvwmScript/Instructions.c=0D
M modules/FvwmScript/Scripts/FvwmScript-BaseConfig=0D
M modules/FvwmScript/Scripts/FvwmScript-BellSetup=0D
M modules/FvwmScript/Scripts/FvwmScript-Buttons=0D
M modules/FvwmScript/Scripts/FvwmScript-Date=0D
M modules/FvwmScript/Scripts/FvwmScript-FileBrowser=0D
M modules/FvwmScript/Scripts/FvwmScript-Find=0D
M modules/FvwmScript/Scripts/FvwmScript-KeyboardSetup=0D
M modules/FvwmScript/Scripts/FvwmScript-PointerSetup=0D
M modules/FvwmScript/Scripts/FvwmScript-Quit=0D
M modules/FvwmScript/Scripts/FvwmScript-ScreenDump=0D
M modules/FvwmScript/Widgets/CheckBox.c=0D
M modules/FvwmScript/Widgets/HDipstick.c=0D
M modules/FvwmScript/Widgets/HScrollBar.c=0D
M modules/FvwmScript/Widgets/ItemDraw.c=0D
M modules/FvwmScript/Widgets/List.c=0D
M modules/FvwmScript/Widgets/Menu.c=0D
M modules/FvwmScript/Widgets/MiniScroll.c=0D
M modules/FvwmScript/Widgets/PopupMenu.c=0D
M modules/FvwmScript/Widgets/PushButton.c=0D
M modules/FvwmScript/Widgets/RadioButton.c=0D
M modules/FvwmScript/Widgets/Rectangle.c=0D
M modules/FvwmScript/Widgets/Swallow.c=0D
M modules/FvwmScript/Widgets/TextField.c=0D
M modules/FvwmScript/Widgets/Tools.c=0D
M modules/FvwmScript/Widgets/Tools.h=0D
M modules/FvwmScript/Widgets/VDipstick.c=0D
M modules/FvwmScript/Widgets/VScrollBar.c=0D
M modules/FvwmScript/Widgets/Widget.c=0D
M modules/FvwmScript/script.c=0D
M modules/FvwmScript/script.y=0D
M modules/FvwmScript/types.h=0D
=0D
Log Message:=0D
-----------=0D
Comments translation.=0D
=0D
=0D
Commit: d48ca181dfaa7ae7c4c90527567d7184701f00c0=0D
https://github.com/fvwmorg/fvwm/commit/d48ca181dfaa7ae7c4c90527567d=
7184701f00c0=0D
Author: Jean Philippe EIMER <[email protected]>=0D
Date: 2020-08-17 (Mon, 17 Aug 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmForm/FvwmForm.1.in=0D
M modules/FvwmForm/FvwmForm.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmForm: change Timeout resolution to 100ms, instead of 1s=0D
=0D
=0D
Commit: 12a4930ffa915399d2f5e1798af03aff27c8b3b5=0D
https://github.com/fvwmorg/fvwm/commit/12a4930ffa915399d2f5e1798af0=
3aff27c8b3b5=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-18 (Tue, 18 Aug 2020)=0D
=0D
Changed paths:=0D
M modules/FvwmMFL/FvwmMFL.c=0D
=0D
Log Message:=0D
-----------=0D
FvwmMFL: add connection_profile=0D
=0D
When a client connects, send through connection_profile, detailing=0D
version information from Fvwm3.=0D
=0D
This will be useful to allow clients to determine what to do with=0D
different Fvwm versions over time.=0D
=0D
=0D
Commit: b9c7aa0618efd3a19e74f8f422a279427fc7f519=0D
https://github.com/fvwmorg/fvwm/commit/b9c7aa0618efd3a19e74f8f422a2=
79427fc7f519=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-21 (Fri, 21 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/Makefile.am=0D
R bin/fvwm-menu-headlines.1=0D
R bin/fvwm-menu-headlines.in=0D
M configure.ac=0D
M default-config/config=0D
=0D
Log Message:=0D
-----------=0D
fvwm-menu-headlines: retire=0D
=0D
fvwm-menu-headlines was originally created to allow the web to be=0D
scraped from various news sites to produce a menu of entries. A great=0D=
idea, but with the advent of RSS feeds and other aggregation programs,=0D=
this script has languished over the years.=0D
=0D
The sites in question no longer function in the way the script assumes,=0D=
and keeping this up to date with largely dynamic HTML and AJAX requests,=0D=
makes this script's job almost impossible to do.=0D
=0D
Goodbye to it.=0D
=0D
=0D
Commit: 0c036f3fcdb146ef3b7df88d1f8a9901ea94f223=0D
https://github.com/fvwmorg/fvwm/commit/0c036f3fcdb146ef3b7df88d1f8a=
9901ea94f223=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-21 (Fri, 21 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/Makefile.am=0D
R bin/fvwm-bug.1.in=0D
R bin/fvwm-bug.in=0D
M bin/fvwm-menu-directory.in=0D
M bin/fvwm-menu-xlock.in=0D
M bin/fvwm-perllib.in=0D
M configure.ac=0D
M doc/index.html=0D
=0D
Log Message:=0D
-----------=0D
fvwm-bug: retire=0D
=0D
fvwm-bug made a lot of sense ~20 years ago when mailing lists were=0D
largely the only way to report bugs to interested parties. Now that=0D
fvwm is hosted on Github, this is where issues/bugs will be filed from=0D=
now one.=0D
=0D
You know, in the modern way...=0D
=0D
=0D
Commit: e4a1a95961bd6f84449ba5e4e0e5368a21e87b23=0D
https://github.com/fvwmorg/fvwm/commit/e4a1a95961bd6f84449ba5e4e0e5=
368a21e87b23=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-25 (Tue, 25 Aug 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
=0D
Log Message:=0D
-----------=0D
configure.ac: look for golang=0D
=0D
Add the required checks to look for golang. Off by default, so needs=0D
--enable-golang explicitly in order to work. Will be used to compile=0D
Fvwm3 modules written in Go, without making this a core dependency.=0D
=0D
=0D
Commit: 09f38d812f84147c73da976549fc7f46f65403ef=0D
https://github.com/fvwmorg/fvwm/commit/09f38d812f84147c73da976549fc=
7f46f65403ef=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-25 (Tue, 25 Aug 2020)=0D
=0D
Changed paths:=0D
M Dockerfile=0D
A bin/FvwmPrompt/.gitignore=0D
A bin/FvwmPrompt/FvwmPrompt.go=0D
A bin/FvwmPrompt/Makefile.am=0D
A bin/FvwmPrompt/go.mod=0D
A bin/FvwmPrompt/go.sum=0D
M bin/Makefile.am=0D
M configure.ac=0D
M modules/FvwmConsole/Makefile.am=0D
=0D
Log Message:=0D
-----------=0D
Introduce FvwmPrompt=0D
=0D
This introduces a new command, FvwmPrompt, as a replacement for=0D
FvwmConsole and FvwmCommand.=0D
=0D
As a replacement for FvwmCommand, it can be run as:=0D
=0D
FvwmPrompt 'fvwm command here'=0D
=0D
As a replacement for FvwmConsole, it can be run as:=0D
=0D
FvwmPrompt=0D
=0D
Unlike FvwmConsole, FvwmPrompt is a standalone program communicating=0D
with FvwmMFL, and is not therefore a Fvwm module. As such, FvwmPrompt=0D=
does not accept the same command-line arguments as FvwmConsole to get it=0D=
to launch a specific terminal (-terminal), for example. Instead, a=0D
compat-friendly shell alias is recommended (but not provided):=0D
=0D
alias FvwmConsole=3D'xterm -g 80x24 -e FvwmPrompt'=0D
=0D
This also means that FvwmPrompt does not need to be started from FVWM=0D
either, and will work as long as "Module FvwmMFL" is running. This is=0D=
the case by default, and hence no configuration changes should be=0D
required to make FvwmMFL load.=0D
=0D
To enable FvwmPrompt, autotools will look for the Go runtime installed=0D=
on the system, and must be at a version >=3D 1.4.x. It must also be told=
=0D
to do this, via --enable-golang, as in:=0D
=0D
./configure --enable-golang=0D
=0D
It is expected in the future that more modules could be written in Go,=0D=
hence this option. It is not currently mandatory that Go needs to be=0D
installed, hence this configure flag.=0D
=0D
If '--enable-golang' is used, and configure checks pass, then this=0D
explicitly bypasses compiling and installing FvwmConsole. This is a=0D
compatibility feature only for now, until such time that confidence in=0D=
FvwmPrompt's use and surrounding tooling on different platforms (BSDs=0D
mostly) is met without any large overhead for package maintainers.=0D
=0D
=0D
Commit: 0a97ed8ec0556b22152dd7ad74b6124c6766eb54=0D
https://github.com/fvwmorg/fvwm/commit/0a97ed8ec0556b22152dd7ad74b6=
124c6766eb54=0D
Author: Mike Qin <[email protected]>=0D
Date: 2020-08-28 (Fri, 28 Aug 2020)=0D
=0D
Changed paths:=0D
M fvwm/menuitem.c=0D
=0D
Log Message:=0D
-----------=0D
fix the vertical alignment when VerticalItemSpacing is large.=0D
=0D
Previous code vertically aligns the text well when VerticalItemSpacing=0D=
is small. However, if VerticalItemSpacing is large, then the font=0D
height + gaps can be larger than MiniIcon's height, and the text will=0D
have an extra y_offset.=0D
=0D
=0D
Commit: c1a10ec374ae7197d58ba9f82e47d4ae1a040593=0D
https://github.com/fvwmorg/fvwm/commit/c1a10ec374ae7197d58ba9f82e47=
d4ae1a040593=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-29 (Sat, 29 Aug 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
=0D
Log Message:=0D
-----------=0D
configure.ac: check for xt=0D
=0D
Don't assume that libxt is installed as part of libx11. On some=0D
systems, libxt is a separate dependency.=0D
=0D
Fixes #191=0D
=0D
=0D
Commit: 9f3ec1bb6314c730f5cb142dfaced65f9aaf719d=0D
https://github.com/fvwmorg/fvwm/commit/9f3ec1bb6314c730f5cb142dface=
d65f9aaf719d=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-29 (Sat, 29 Aug 2020)=0D
=0D
Changed paths:=0D
M fvwm/add_window.c=0D
=0D
Log Message:=0D
-----------=0D
Revert "used_sm: skip setup of maximized windows"=0D
=0D
This reverts commit cf96e02f661ea55010f6eb436e76d7331d093132.=0D
=0D
=0D
Commit: 8693eaa8ffbd3d61053b5bbece3be2d55aca5a54=0D
https://github.com/fvwmorg/fvwm/commit/8693eaa8ffbd3d61053b5bbece3b=
e2d55aca5a54=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-29 (Sat, 29 Aug 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
Revert "placement: don't alter desk during restarts/recaptures"=0D
=0D
This reverts commit cdf9975b362bce8d85407f8ad6dc8c73a1a24e80.=0D
=0D
=0D
Commit: 0a459cfce55156e665700b32a01fd622c38aae1a=0D
https://github.com/fvwmorg/fvwm/commit/0a459cfce55156e665700b32a01f=
d622c38aae1a=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-29 (Sat, 29 Aug 2020)=0D
=0D
Changed paths:=0D
M bin/FvwmPrompt/FvwmPrompt.go=0D
=0D
Log Message:=0D
-----------=0D
FvwmPrompt: don't lowercase all commands=0D
=0D
Certain commands sent to Fvwm3 need the case to be intact as commands=0D
such as modules look for files on disk (i.e. FvwmButtons vs=0D
fvwmbuttons).=0D
=0D
Leave the case alone.=0D
=0D
=0D
Commit: c88af4503a011490167e0bb441c294426fa9608e=0D
https://github.com/fvwmorg/fvwm/commit/c88af4503a011490167e0bb441c2=
94426fa9608e=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-31 (Mon, 31 Aug 2020)=0D
=0D
Changed paths:=0D
M fvwm/placement.c=0D
=0D
Log Message:=0D
-----------=0D
Revert "Revert "placement: don't alter desk during restarts/recaptures"=
"=0D
=0D
This reverts commit 8693eaa8ffbd3d61053b5bbece3be2d55aca5a54.=0D
=0D
=0D
Commit: 7d8837106ba1f3b5f9de3dc15d86dd774a2895f1=0D
https://github.com/fvwmorg/fvwm/commit/7d8837106ba1f3b5f9de3dc15d86=
dd774a2895f1=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-08-31 (Mon, 31 Aug 2020)=0D
=0D
Changed paths:=0D
M fvwm/session.c=0D
=0D
Log Message:=0D
-----------=0D
Revert "session: make monitor checks more robust"=0D
=0D
This reverts commit 86038344d4240469d86677ae3403ade0a3ba0671.=0D
=0D
=0D
Commit: 068fd6e6dee6fb6283c1401da989b24632f32df5=0D
https://github.com/fvwmorg/fvwm/commit/068fd6e6dee6fb6283c1401da989=
b24632f32df5=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-09-01 (Tue, 01 Sep 2020)=0D
=0D
Changed paths:=0D
M dev-docs/INSTALL.md=0D
=0D
Log Message:=0D
-----------=0D
Update INSTALL.md=0D
=0D
Remove confusing sentence about core/optional dependencies; the headings =
are good enough.=0D
=0D
=0D
Commit: 6cc8d272c9198244c6ba66298ab7251b61bc795c=0D
https://github.com/fvwmorg/fvwm/commit/6cc8d272c9198244c6ba66298ab7=
251b61bc795c=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-09-03 (Thu, 03 Sep 2020)=0D
=0D
Changed paths:=0D
M configure.ac=0D
M utils/fvwm-version-str.sh=0D
=0D
Log Message:=0D
-----------=0D
Fvwm3-RC-0=0D
=0D
=0D
Commit: bd76409bb147a8426b3ea102aac3f7c6277d2619=0D
https://github.com/fvwmorg/fvwm/commit/bd76409bb147a8426b3ea102aac3=
f7c6277d2619=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-09-03 (Thu, 03 Sep 2020)=0D
=0D
Changed paths:=0D
M fvwm/events.c=0D
=0D
Log Message:=0D
-----------=0D
KeepRaised: be kinder to iconified windows=0D
=0D
When recapturing windows, ensure iconfied widnows are treated kinder=0D
before attempting to transition them to NormalState, otherwise they=0D
won't stay iconified for long.=0D
=0D
Noticed by okraits on IRC.=0D
=0D
=0D
Commit: 6160acbd5ba703ac2985531714538a5bbe408bf8=0D
https://github.com/fvwmorg/fvwm/commit/6160acbd5ba703ac298553171453=
8a5bbe408bf8=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-09-03 (Thu, 03 Sep 2020)=0D
=0D
Changed paths:=0D
M fvwm/fvwm3.c=0D
=0D
Log Message:=0D
-----------=0D
Env: add FVWM_IS_FVWM3 envvar=0D
=0D
Because fvwm3's version checking resets to 1.0.0, this makes things=0D
awkward for people trying to reuse their existing fvwm2 configs,=0D
especially if they're checking for a string such as >=3D2.6=0D
=0D
Since >2.6 won't work to imply fvwm3 (and that this will be removed in=0D=
fvwm3 soon anyway), instead provide an environment variable:=0D
FVWM_IS_FVWM3 which can be used with EnvIsSet test condition.=0D
=0D
Somewhat addresses #195 but not fully. See the comments therein.=0D
=0D
=0D
Commit: d79d31272cb403af8fe498c285e42af570e6ba60=0D
https://github.com/fvwmorg/fvwm/commit/d79d31272cb403af8fe498c285e4=
2af570e6ba60=0D
Author: Thomas Adam <[email protected]>=0D
Date: 2020-09-03 (Thu, 03 Sep 2020)=0D
=0D
Changed paths:=0D
M bin/Makefile.am=0D
M configure.ac=0D
M doc/fvwm/sections=0D
M utils/fvwm-version-str.sh=0D
=0D
Log Message:=0D
-----------=0D
Release 1.0.0=0D
=0D
Version 1.0.0 released.=0D
=0D
=0D
Compare: https://github.com/fvwmorg/fvwm/compare/55a5893adb4e%5E...d79d31=
272cb4=0D