Re: FVWM: The Future of fvwm Development

2016-11-23 Thread doark
On Fri, 18 Nov 2016 12:18:15 Jaimos Skriletz wrote: > On Wed, Nov 16, 2016 at 4:43 PM, David Niklas wrote: > > On Fri, 11 Nov 2016 23:13:49 + > > > > Not so much a question as a comment. > > Many window managers and desktop environments have tried in vain to > > create an automatic menu gene

Re: FVWM: The Future of fvwm Development

2016-11-18 Thread Stuart Longland
On 19/11/16 06:22, Dominik Vogt wrote: > It war certainly fun to code. :-) ^ And a fight to debug? ;-) -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere. signature.asc Description: OpenPGP digital signature

Re: FVWM: The Future of fvwm Development

2016-11-18 Thread Dominik Vogt
On Fri, Nov 18, 2016 at 12:18:15PM -0700, Jaimos Skriletz wrote: > On Wed, Nov 16, 2016 at 4:43 PM, David Niklas wrote: > > On Fri, 11 Nov 2016 23:13:49 + > > > > Not so much a question as a comment. > > Many window managers and desktop environments have tried in vain to create > > an automati

Re: FVWM: The Future of fvwm Development

2016-11-18 Thread Jaimos Skriletz
On Wed, Nov 16, 2016 at 4:43 PM, David Niklas wrote: > On Fri, 11 Nov 2016 23:13:49 + > > Not so much a question as a comment. > Many window managers and desktop environments have tried in vain to create > an automatic menu generator without success, I recommend that fvwm does > not attempt to

Re: FVWM: The Future of fvwm Development

2016-11-18 Thread David Niklas
On Fri, 11 Nov 2016 23:13:49 + Thomas Adam wrote: > Hello all, > > For those of you who follow fvwm-workers@ may already know some of > this, but for those of you who don't, it's worth mentioning what the > state of fvwm development holds for the future. > > We have been discussing a lot ab

Re: FVWM: The Future of fvwm Development

2016-11-15 Thread Dominik Vogt
On Tue, Nov 15, 2016 at 10:30:10AM +0100, Harald Dunkel wrote: > On 11/12/2016 07:59 AM, Marco Maggi wrote: > > > > I do not follow the devel mailing list. There is a single very > > selfish request I have: continue to allow fvwm to fully configure the > > use of the keyboard (I have