Re: FVWM: The Future of fvwm Development

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

Re: FVWM: The Future of fvwm Development

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

Re: FVWM: The Future of fvwm Development

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

Re: FVWM: The Future of fvwm Development

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

Re: FVWM: The Future of fvwm Development

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 fvwm intercept the function keys (F1, ...) > to do stuff for me, and

Re: FVWM: The Future of fvwm Development

Thomas Adam wrote: > 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. I am a long time fvwm user, and I have not touched my ".fvwmrc" in years because it