Mikhael Goikhman [EMAIL PROTECTED] wrote:
Like other posters, I don't quite like that names are sudently work
using logical OR while all other options in conditional commands work
using logical AND. And the nagations of names work using AND again.
Here is the proposal that should solve all these
Hi Norman,
About a month ago, I sent in a patch to allow multiple window names in
conditions.
I think being able to specify multiple windows in conditions is very
useful.
It's 2:30am ... let me see if I understand your patch correctly:
If you have:
Next (mozilla dillo netscape) Function ...
On Wed, Jul 07, 2004 at 02:28:23AM +1000, Scott Smedley wrote:
Hi Norman,
About a month ago, I sent in a patch to allow multiple window names in
conditions.
I think being able to specify multiple windows in conditions is very
useful.
It's 2:30am ... let me see if I understand your patch
On 31 May 2004 21:53:51 -0400, Norman Yarvin wrote:
This is a small patch that allows multiple window names to be specified
in conditions. I've tried to write it with the same style used in the
rest of the code, although some variable names may be a bit terse by your
standards. The patch
About a month ago, I sent in a patch to allow multiple window names in
conditions. It was developed for my own use, but since I am a lazy guy,
I was hoping the fvwm workers would pick it up, so I wouldn't have to
keep maintaining it. That doesn't seem to have happened. Perhaps I
should have
Craig wrote:
Next (Netscape konqueror Mozilla*) WarpToWindow 99 90
This is a nice implementation of an OR rule, is there any way of specifying
and AND rule? For example, a rule to match a window with Class Netscape
and Title local*. Now that multiple window names can be read, why not
Next (Netscape konqueror Mozilla*) WarpToWindow 99 90
This is a nice implementation of an OR rule, is there any way of specifying
and AND rule? For example, a rule to match a window with Class Netscape
and Title local*. Now that multiple window names can be read, why not
include one.
For
