Re: An *operator's guide to fvwm?

On Mon 26 Feb 2018 at 20:24:28 (+0100), Thomas Schmitt wrote: > Hi, > > Richard Owlett wrote: > > Without *ANY* customization, how much more can fvwm do for me? > > Without any customization by anybody it is quite useless. Lest this give the wrong impression to someone coming across this post,

Re: An *operator's" guide to fvwm?

On Mon, 26 Feb 2018 10:17:46 -0600 John Hasler sent: > BTW you should be editing ~/.fvwm/config if you are using the current > release. The 2 was dropped from fvwm2 a long time ago and all fvwm > related files placed under ~/.fvwm with config being the default > configuration file.

Re: An *operator's guide to fvwm?

On 02/26/2018 01:24 PM, Thomas Schmitt wrote: Hi, Richard Owlett wrote: Without *ANY* customization, how much more can fvwm do for me? Without any customization by anybody it is quite useless. *ROFL* It may have aesthetic problems. BUT My real world needs (not glittzy desires) were handled

Re: An *operator's guide to fvwm?

Hi, Richard Owlett wrote: > Without *ANY* customization, how much more can fvwm do for me? Without any customization by anybody it is quite useless. With reasonable customization by an initial ~/.fvwm2rc and some additions by myself, it does for me: - Add handles to the windows so i can move,

Re: An *operator's" guide to fvwm?

On Mon 26 Feb 2018 at 12:42:25 (-0600), Richard Owlett wrote: > On 02/26/2018 10:54 AM, Michelle Konzack wrote: > >Hi, > > > >Am 2018-02-26 hackte Richard Owlett in die Tasten: > >>I am finding lots of information on detailed low level configuration: > >>e.g.

Re: An *operator's" guide to fvwm?

On 02/26/2018 12:12 PM, Curt wrote: On 2018-02-26, Richard Owlett wrote: Ahh, but a Flocken Elektrowagen might today may be more functional in some circumstances than a Rolls Royce. http://www.circuitousroot.com/artifice/programming/useful/fvwm/index.html

Re: An *operator's" guide to fvwm?

On 02/26/2018 10:54 AM, Michelle Konzack wrote: Hi, Am 2018-02-26 hackte Richard Owlett in die Tasten: I am finding lots of information on detailed low level configuration: e.g. I'm using almost a default install changing only the wallpaper and the

Re: An *operator's" guide to fvwm?

On 2018-02-26, Richard Owlett wrote: > > Ahh, but a Flocken Elektrowagen might today may be more functional in > some circumstances than a Rolls Royce. > http://www.circuitousroot.com/artifice/programming/useful/fvwm/index.html I only read the nice discussion of "Viewports

Re: An *operator's" guide to fvwm?

Richard Owlett writes: > I remember 026's as the normal input device and a UART was square > inches of a double sided board. So do I. I kept on learning. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: An *operator's" guide to fvwm?

On 02/26/2018 10:32 AM, Steve McIntyre wrote: Richard Owlett wrote: On 02/26/2018 09:23 AM, David Wright wrote: https://lists.debian.org/debian-user/2018/02/msg00752.html Two of the references there were straightforward to use when I posted this, but now you'll have to temporarily accept an

Re: An *operator's" guide to fvwm?

On 02/26/2018 10:17 AM, John Hasler wrote: Richard Owlett writes: Already had them bookmarked. They, like , might be compared to an _Owner's Manual". I'm looking for something more like an _Operator's Manual_. The target audience of what I'm

Re: An *operator's" guide to fvwm?

Hi, Am 2018-02-26 hackte Richard Owlett in die Tasten: > I am finding lots of information on detailed low level configuration: > e.g. > > I'm using almost a default install changing only the wallpaper and the > default font size for menus. > > I'm

Re: An *operator's" guide to fvwm?

Richard Owlett wrote: >On 02/26/2018 09:23 AM, David Wright wrote: >> >> https://lists.debian.org/debian-user/2018/02/msg00752.html >> >> Two of the references there were straightforward to use when I posted >> this, but now you'll have to temporarily accept an expired certificate. > >Already

Re: An *operator's" guide to fvwm?

Richard Owlett writes: > Already had them bookmarked. They, like > , might be compared to an > _Owner's Manual". I'm looking for something more like an _Operator's > Manual_. > The target audience of what I'm looking for would have no need to edit >

Re: An *operator's" guide to fvwm?

On 02/26/2018 09:23 AM, David Wright wrote: On Mon 26 Feb 2018 at 08:15:44 (-0600), Richard Owlett wrote: I am finding lots of information on detailed low level configuration: e.g. I'm using almost a default install changing only the wallpaper and

Re: An *operator's" guide to fvwm?

On Mon 26 Feb 2018 at 08:15:44 (-0600), Richard Owlett wrote: > I am finding lots of information on detailed low level configuration: > e.g. > > I'm using almost a default install changing only the wallpaper and > the default font size for menus. > >

Re: An *operator's guide to fvwm?

On 02/26/2018 08:54 AM, Thomas Schmitt wrote: Hi, Richard Owlett wrote: http://zensites.net/fvwm/guide/index.html That's a quick tour through a few gestures of fvwm. Maybe it gives you some ideas for playing with the configuration. But obviously you want something different. "not seeing

Re: An *operator's guide to fvwm?

Hi, Richard Owlett wrote: > http://zensites.net/fvwm/guide/index.html That's a quick tour through a few gestures of fvwm. Maybe it gives you some ideas for playing with the configuration. But obviously you want something different. > "not seeing the trees for the leaves" Ok. What forest do

Re: An *operator's" guide to fvwm?

On 2018-02-26, Richard Owlett wrote: > I am finding lots of information on detailed low level configuration: > e.g. > > I'm using almost a default install changing only the wallpaper and the > default font size for menus. > > I'm