Re: FVWM: Ideas for a new configration file

2016-07-09 Thread Thomas Adam
On Sun, Jun 12, 2016 at 01:28:25AM +0200, Thomas Funk wrote: > > Btw ... Thomas, do you have already the latest tarball of Nicks and your work? > It would be very interesting to have a look at it :-) So it turns out I did. To that end, I simply took the files and put them in the right place, the

Re: FVWM: Ideas for a new configration file

2016-06-12 Thread Thomas Adam
On 12 June 2016 at 00:28, Thomas Funk wrote: > Btw ... Thomas, do you have already the latest tarball of Nicks and your > work? > It would be very interesting to have a look at it :-) No. -- Thomas Adam

Re: FVWM: Ideas for a new configration file

2016-06-11 Thread Thomas Funk
On 06/10/2016 03:06 PM, Thomas Adam wrote: Hello all, As some of you may be aware, the master branch in git now has code which not only removes a lot of older modules, but also removes any mechanism for having a default configuration. There was a previous discussion on having a new default conf

Re: FVWM: Ideas for a new configration file

2016-06-10 Thread Tom Horsley
On Fri, 10 Jun 2016 14:06:03 +0100 Thomas Adam wrote: > Opinions and thoughts welcome. I definitely wanted to make my init file completely mine, and one of the problems I ran into was not knowing that lots of default settings were built into fvwm, so it took a while for me to find and squash the

FVWM: Ideas for a new configration file

2016-06-10 Thread Thomas Adam
Hello all, As some of you may be aware, the master branch in git now has code which not only removes a lot of older modules, but also removes any mechanism for having a default configuration. There was a previous discussion on having a new default configuration file here: http://thread.gmane.org