File: HISTORY

package info (click to toggle)
wmanager 0.3.1-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 244 kB
  • sloc: cpp: 497; python: 411; perl: 124; makefile: 108; sh: 83
file content (47 lines) | stat: -rw-r--r-- 1,921 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
v0.1 1999/09/26:
	- started this project

v0.1.1 1999/10/05:
        - added alternative .wmanagerrc file support
	- fixed bug in Makefile
	- added disclaimer text

v0.2.1 2002/08/19:
	- misc fixes (including a braindamaged 'return 1')

v0.2.2 2016/11/04
	- adopted by Peter Pentchev with Dr. Meik Teßmer's kind permission
	- set up a Git repository on GitLab
	- applied patches by Martin Michlmayr <tbm@cyrius.com>,
	  Branden Robinson <branden@progeny.com>,
	  James Troup <james@nocrew.org>, Andreas Rottmann <rotty@debian.org>,
	  Tommi Virtanen <tv@debian.org>, and myself to fix the build
	- switched to fltk-config instead of hardcoding the compiler flags
	  and linker libraries
	- dropped the "static" Makefile target
	- removed the VCS tags ($Id, etc) that are not automatically
	  expanded by the Git version control system
	- removed the Java classes, HTML templates, and CSS files for
	  the autogenerated C++ class documentation since the tool used
	  for generating it is not available any more
	- reworded some of the documentation files
	- added the wmanager manual page and the wmanager-loop and
	  wmanagerrc-update tools from the Debian package

v0.3.0 2020/07/15
	- made it possible for the window manager path to include
	  an equals sign ("=")
	- removed some diagnostic output when the -r option is used
	- applied some reliability fixes to the wmanager-loop tool

v0.3.1 2022/08/09
	- fix an out-of-bounds memory write when parsing the -r command-line
	  option; thanks to Simon Chopin for finding and fixing the problem!
	- run the test suite using the Tox tool
	- refresh the Python coding style for the test tool:
	  - reformat the source code using the black tool
	  - simplify the type annotations syntax
	  - use subprocess.run() as appropriate
	  - use subprocess.Popen() as a context manager as appropriate
	- add an EditorConfig definitions file
	- use tabs in the .xinitrc sample file