Re: FVWM: Look for FvwmCpp and FvwmM4 best practice.

2012-07-09 Thread Oleksandr Gavenko
On 2012-07-09, Dan Espen wrote: > Oleksandr Gavenko writes: > >> On 2012-07-08, Thomas Adam wrote: >> >>> On Sun, Jul 08, 2012 at 05:20:28PM +0300, Oleksandr Gavenko wrote: >> Now I think that FvwmCpp and FvwmM4 are mostly useless modules. > > Little snippet from one of my config files: > > #defi

Re: FVWM: Look for FvwmCpp and FvwmM4 best practice.

2012-07-08 Thread Dan Espen
Oleksandr Gavenko writes: > On 2012-07-08, Thomas Adam wrote: > >> On Sun, Jul 08, 2012 at 05:20:28PM +0300, Oleksandr Gavenko wrote: > Now I think that FvwmCpp and FvwmM4 are mostly useless modules. Little snippet from one of my config files: #define BACK 21/B9/FD #define FORE 22/59/E9 Destroy

Re: FVWM: Look for FvwmCpp and FvwmM4 best practice.

2012-07-08 Thread Oleksandr Gavenko
On 2012-07-08, Thomas Adam wrote: > On Sun, Jul 08, 2012 at 05:20:28PM +0300, Oleksandr Gavenko wrote: >> >> SetVar VAR VAL > > That's why I wrote the InfoStore command. > Ok, I get it: http://www.mail-archive.com/fvwm-workers@fvwm.org/msg02706.html and new docs says about it: http://www

Re: FVWM: Look for FvwmCpp and FvwmM4 best practice.

2012-07-08 Thread Thomas Adam
On Sun, Jul 08, 2012 at 05:20:28PM +0300, Oleksandr Gavenko wrote: > Firstly I make some explanation. Next I ask questions. Sorry for long text (( > > > > I have: > > SetVar VAR VAL > > in my .fvwmrc but this is not good to expo

FVWM: Look for FvwmCpp and FvwmM4 best practice.

2012-07-08 Thread Oleksandr Gavenko
Firstly I make some explanation. Next I ask questions. Sorry for long text (( I have: SetVar VAR VAL in my .fvwmrc but this is not good to export them to other processes (this happen when I call application from Fvwm menu). Pag