On 22 Apr 2004 10:10:20 +0200, Markus Schwarzenberg wrote: > > On Wed, 21 Apr 2004 21:26:13 +0000 Mikhael Goikhman <[EMAIL PROTECTED]> > wrote: > > > On 21 Apr 2004 09:48:48 +0200, Markus Schwarzenberg wrote: > > > > > > for a long time I've been using a small patch to fvwm 2.4.8, (which > > > now is adopted to 2.4.18 and 2.5.10, too) and would like to ask if > > > other people find it usefull too (so it could be included into the > > > fvwm source one day): > > > > > > Description: > > > > > > The patch adds the following syntax to Condition checks to > > > selectively select a match (or mismatch) of a name, icon name, > > > resource name or class: > > > > > > %r==RESOURCE > > > %c==CLASS > > > %i==ICONNAME > > > %n==NAME > > > > > > %r!=RESOURCE > > > %c!=CLASS > > > %i!=ICONNAME > > > %n!=NAME > > > > IMO the syntax should be more readable: > > > > ThisWindow (Class XTerm, !Resource RTerm, !Resource ATerm) Beep > > This would introduce more ambiguousness, since conditions still may > be separated by whitespaces or commas. In the example above it's not > clear how to interpret "Class": Is it a window name, icon name, > class name or resource name or a special match identifier?
I don't think there is any ambiguousness, just always interpret strings "Class" and similar specially. This does not introduce any problem if a user uses comma (preferred and hopefully the only syntax in the future). We already use special keywords in conditions: State, Layer. In any case, this is less ambiguous than to interpret substrings '%', '==' and '!=' in names specially. > The syntax proposed by you would be OK if whitespaces were > abolished as condition separators. This is a long-term intention for all commands. Commas are only optional if there is no ambiguity, otherwise they are mandatory. I don't oppose to issue warnings when commas are missing. 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]
