On 19 Nov 2002 12:35:32 +0100, Dominik Vogt wrote: > > On Tue, Nov 19, 2002 at 11:04:26AM +0000, Mikhael Goikhman wrote: > > On 18 Nov 2002 12:34:03 -0800, [EMAIL PROTECTED] wrote: > > > > > > > - Changed some defaults (not META_L binding by default; no default > > > > font; use mouse selection). > > > > > > Does everyone actually want the proxies to be auto-selected by moving the > > > mouse > > > over them and not even clicking them? I found it really annoying, but > > > I'd be > > > willing to put it up for a vote. > > > > If you speak about ConfigFvwmProxyDefaults, it is only an example > > configuration, it may include anything to help a user to understand the > > usage, but it is not going to be included (read forced) for everyone, > > just like we don't include any configuration for our 30 other modules. > > > > I suppose Dominik only temporarily forced this file for everyone. > > Actually, no. In the case of FvwmProxy, I wanted to provide a > neat interface for module/fvwm communication. We can hardly > expect that a normal user can write this on her own or copy it > from the man page. Think of it as part of the deafult interface. > > ----------------------- snip --------------------- > AddToFunc FvwmProxyShowFunc > + I UnsetEnv FvwmProxy_S > > ... > > AddToFunc FvwmProxy_Mark > + I SendToModule FvwmProxy mark $w > > AddToFunc FvwmProxy_Circulate > + I WindowId $[FvwmProxy_S] $0 $1 FvwmProxy_Mark > + I CondCase (Error) $0 $1 FvwmProxy_Mark > ----------------------- snip --------------------- > > But that does not mean I want this for every module.
As much as one likes some module (FvwmAnimate, FvwmBanner, FvwmTheme, FvwmBacker, FvwmProxy) fvwm should be able to start naked without requiring/configuring anything like this. The more configuration we force for everyone the more an experienced user should undo for his own setup. It is also unexpecting that the man page says something about the defaults and a user gets something different. If FvwmProxy can't work without defining some functions, it should ask fvwm to create them, but if these functions are optional and configurable, one example implementation should not be forced for everyone. I think the good solution is to mention in the man page that to get one predefined FvwmProxy configuration a user may include 2 lines to his config (but do not force these lines for him): Read ConfigFvwmProxyDefaults AddToFunc StartFunction I FvwmProxy Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
