On 09 May 2004 13:03:19 +0100, Tavis Ormandy wrote: > > --On Sunday, May 09, 2004 12:17:48 +0100 Tavis Ormandy > <[EMAIL PROTECTED]> wrote: > > > > --On Saturday, May 08, 2004 22:53:27 +0000 Mikhael Goikhman > > <[EMAIL PROTECTED]> wrote: > > > >> IMHO, the Test condition should default to true just like with all other > >> conditional commands. > > > > I see, how about changing the test for "True" to check for "False"? > > Maybe I should expand on that, for example, right now: > > Test (True) This will happen > Test (False) This will happen > Test (Blahblahblah) This will happen
The last command should produce a syntax error, bad if it does not. The Test command does not check that an arbitrary string is true, it checks that the named condition is satisfied. > but True is still tested for as an on-condition, if this was changed to > check for False and set match accordingly: > > Test (True) This will happen > Test (False) This wont happen > Test (Blahblahblah) This will happen > > so Test still defaults to a match, what do you think? I think you misuse the intended condition syntax. As I said, you just want a new IsEmpty or maybe IsTrue condition, i.e.: Test (IsTrue "$0") happens conditionally 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]
