Re: killmodules does not handle module aliases
On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > How difficult is it to make module aliases to work with KillModule > too? This works since 2.3.x: Module FvwmButtons MyLeftTopBar KillModule FvwmButtons MyLeftTopBar And "KillModule FvwmButtons" kills all aliases. Regards, Mikhael. -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
On Thu, Mar 27, 2003 at 01:35:05PM +, Mikhael Goikhman wrote: > On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > > > How difficult is it to make module aliases to work with KillModule > > too? > > This works since 2.3.x: > > Module FvwmButtons MyLeftTopBar > KillModule FvwmButtons MyLeftTopBar > > And "KillModule FvwmButtons" kills all aliases. I see. Is there any reason why I can't say just KillModule MyLeftTopBar ? Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
On 27 Mar 2003 15:15:30 +0100, Dominik Vogt wrote: > > On Thu, Mar 27, 2003 at 01:35:05PM +, Mikhael Goikhman wrote: > > On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > > > > > How difficult is it to make module aliases to work with KillModule > > > too? > > > > This works since 2.3.x: > > > > Module FvwmButtons MyLeftTopBar > > KillModule FvwmButtons MyLeftTopBar > > > > And "KillModule FvwmButtons" kills all aliases. > > I see. Is there any reason why I can't say just > > KillModule MyLeftTopBar Will then "KillModule FvwmButtons" mean kill only one alias (no alias) or all aliases? Currently you can do both variants (for example, I use "KillModule FvwmEvent to kill all event listeners). This was the reason of this KillModule syntax, another reason is similarity of the Module and KillModule syntaxes regarding aliases. Finally, currently you may define "Module FvwmIconMan MyLeftTopBar" and it works. The global problem we have with aliases is that alias is optional for modules, once we make the alias concept to be mandatory for all modules, we may then think about changing the syntax of all module commands. I will start a new thread about this later. Regards, Mikhael. -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
On Thu, Mar 27, 2003 at 03:24:32PM +, Mikhael Goikhman wrote: > On 27 Mar 2003 15:15:30 +0100, Dominik Vogt wrote: > > > > On Thu, Mar 27, 2003 at 01:35:05PM +, Mikhael Goikhman wrote: > > > On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > > > > > > > How difficult is it to make module aliases to work with KillModule > > > > too? > > > > > > This works since 2.3.x: > > > > > > Module FvwmButtons MyLeftTopBar > > > KillModule FvwmButtons MyLeftTopBar > > > > > > And "KillModule FvwmButtons" kills all aliases. > > > > I see. Is there any reason why I can't say just > > > > KillModule MyLeftTopBar > > Will then "KillModule FvwmButtons" mean kill only one alias (no alias) > or all aliases? Only one. How about pattern matching as in DestroyModuleConfig: KillModule FvwmButtons* ? > Currently you can do both variants (for example, I use > "KillModule FvwmEvent to kill all event listeners). This was the reason > of this KillModule syntax, another reason is similarity of the Module > and KillModule syntaxes regarding aliases. Finally, currently you may > define "Module FvwmIconMan MyLeftTopBar" and it works. > > The global problem we have with aliases is that alias is optional for > modules, once we make the alias concept to be mandatory for all modules, > we may then think about changing the syntax of all module commands. > I will start a new thread about this later. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
On 27 Mar 2003 16:35:33 +0100, Dominik Vogt wrote: > > On Thu, Mar 27, 2003 at 03:24:32PM +, Mikhael Goikhman wrote: > > On 27 Mar 2003 15:15:30 +0100, Dominik Vogt wrote: > > > > > > On Thu, Mar 27, 2003 at 01:35:05PM +, Mikhael Goikhman wrote: > > > > On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > > > > > > > > > How difficult is it to make module aliases to work with KillModule > > > > > too? > > > > > > > > This works since 2.3.x: > > > > > > > > Module FvwmButtons MyLeftTopBar > > > > KillModule FvwmButtons MyLeftTopBar > > > > > > > > And "KillModule FvwmButtons" kills all aliases. > > > > > > I see. Is there any reason why I can't say just > > > > > > KillModule MyLeftTopBar > > > > Will then "KillModule FvwmButtons" mean kill only one alias (no alias) > > or all aliases? > > Only one. This breaks compatibility with the way it always worked (all FvwmButtons instances are closed) and does not add anything that is not already possible using KillModule. > How about pattern matching as in DestroyModuleConfig: > > KillModule FvwmButtons* Pattern on what? Module name (the first Module argument) or module alias (usually the second Module argument, but not always, it's heuristics)? I don't like the way we currently mix these two, we did this in the past, but we should not do this in the future if we want a non-ambiguous clean way of working with modules. We should have 2 levels, one for module names and one for instance names instead of global mixing of everything in one namespace. I have a proper and convenient solution for this, but it is a bit revolutional to be discussed now. Maybe after 2.6. Regards, Mikhael. -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
On Fri, Mar 28, 2003 at 01:19:39AM +, Mikhael Goikhman wrote: > On 27 Mar 2003 16:35:33 +0100, Dominik Vogt wrote: > > > > On Thu, Mar 27, 2003 at 03:24:32PM +, Mikhael Goikhman wrote: > > > On 27 Mar 2003 15:15:30 +0100, Dominik Vogt wrote: > > > > > > > > On Thu, Mar 27, 2003 at 01:35:05PM +, Mikhael Goikhman wrote: > > > > > On 27 Mar 2003 14:27:30 +0100, Dominik Vogt wrote: > > > > > > > > > > > > How difficult is it to make module aliases to work with KillModule > > > > > > too? > > > > > > > > > > This works since 2.3.x: > > > > > > > > > > Module FvwmButtons MyLeftTopBar > > > > > KillModule FvwmButtons MyLeftTopBar > > > > > > > > > > And "KillModule FvwmButtons" kills all aliases. > > > > > > > > I see. Is there any reason why I can't say just > > > > > > > > KillModule MyLeftTopBar > > > > > > Will then "KillModule FvwmButtons" mean kill only one alias (no alias) > > > or all aliases? > > > > Only one. > > This breaks compatibility with the way it always worked (all FvwmButtons > instances are closed) and does not add anything that is not already > possible using KillModule. It adds an intuitive syntax. > > How about pattern matching as in DestroyModuleConfig: > > > > KillModule FvwmButtons* > > Pattern on what? Module name (the first Module argument) or module alias > (usually the second Module argument, but not always, it's heuristics)? > I don't like the way we currently mix these two, we did this in the past, > but we should not do this in the future if we want a non-ambiguous clean > way of working with modules. We should have 2 levels, one for module > names and one for instance names instead of global mixing of everything > in one namespace. *Shrug* At the cost of nobody knowing the syntax. > I have a proper and convenient solution for this, but it is a bit > revolutional to be discussed now. Maybe after 2.6. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at 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]
Re: killmodules does not handle module aliases
As I said in the parent messages, I want to rework module aliases before 3.0, i.e. finally add a concept of aliases to the module protocol and adjust all module commands. Adding now a syntax that 1) does not add any new functionality, 2) breaks compatibility, 3) may kill a wrong module in some infortunate cases, since the alias name currently is determined by heuristics, 4) will be removed soon when the real solution for module aliases is implemented, does not seem a proper thing to do for me. Regards, Mikhael. -- Visit the official FVWM web page at 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]
