fix match limits in apps file, plus some documentation

9 files changed, 153 insertions, 184 deletions

diff --git a/doc/asciidoc/fluxbox-keys.txt b/doc/asciidoc/fluxbox-keys.txt
index b3b458a..8ba93ca 100644
--- a/doc/asciidoc/fluxbox-keys.txt
+++ b/doc/asciidoc/fluxbox-keys.txt
@@ -208,8 +208,8 @@ These commands ordinarily affect only the currently focused window. The
 
 *SetDecor* 'decor'::
         Sets which window decorations will be shown. 'decor' has the same format
-        as the `[Deco]' parameter in the apps file. See man fluxbox section
-        APPLICATION SETTINGS for more info.
+        as the `[Deco]' parameter in the apps file. See `man fluxbox' section
+        APPLICATIONS for more info.
 
 *ToggleDecor*::
         Toggles the presence of the window decorations (title bar, window
@@ -556,9 +556,6 @@ properties specified in the 'pattern'. A 'pattern' looks like this:
 
 (['propertyname'[!]=]'regexp') ...
 
-That is, one or more match definitions, followed by an optional limit on the
-number of windows to match.
-
 Match definitions are enclosed in parentheses *(*...*)*, and if no
 'propertyname' is given then *Name* is assumed. The 'regexp' can contain any
 regular expression, or the special value *[current]*, which matches the
diff --git a/doc/asciidoc/fluxbox.1 b/doc/asciidoc/fluxbox.1
index 4d14f71..0272673 100644
--- a/doc/asciidoc/fluxbox.1
+++ b/doc/asciidoc/fluxbox.1
@@ -1,11 +1,11 @@
 .\"     Title: fluxbox
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
-.\"      Date: 08/19/2008
+.\"      Date: 08/20/2008
 .\"    Manual: 
 .\"    Source: 
 .\"
-.TH "FLUXBOX" "1" "08/19/2008" "" ""
+.TH "FLUXBOX" "1" "08/20/2008" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -1199,40 +1199,44 @@ The default installation of fluxbox provides some of these style files\. See flu
 In addition to the style file, the overlay file, whose location is specified by session\.screen0\.styleOverlay (default: ~/\.fluxbox/overlay ) can be used to set style resources that override all styles\. For more information about which parts of fluxbox can be controlled by the overlay file, see fluxstyle(1)\.
 .sp
 .SH "APPLICATIONS"
-It is possible to force an application to always have the same dimensions, position, and other settings when it is first launched\. This is done using either the window\-menu `Remember\&...\fI submenu, or by directly using the ~/\.fluxbox/apps file\. Be careful about editing the apps file while fluxbox is running\. Your changes may be overwritten\. Following is a listing of the valid entries for the `apps\fR file\. The `Remember\&...\fI submenu has entries for most options that store the current state in the `apps\fR file for future use\.
+It is possible to force an application to always have the same dimensions, position, and other settings when it is first launched\. The easiest way to do this is to use the `Remember\&...\' submenu of the window menu, which can usually be opened with a right click on the titlebar\. More advanced features require manually editing the ~/\.fluxbox/apps file, where these settings are saved\.
 .sp
-The format of a line in the `apps\' file is:
+The format of a section in the `apps\' file is:
 .sp
 .sp
 .RS 4
 .nf
-[app] (app\-name) {count \- optional}
-    [Property1]  {value1}
-    [Property2]  {value2}
+[app] (Property=\'value\') \.\.\. {count \- optional}
+    [Setting1]  {value1}
+    [Setting2]  {value2}
     \.\.\.
 [end]
 .fi
 .RE
-Each app\-name can be a string, or a regular expression\. By default the name is matched against a window\'s WM_CLASS property (the first string in it, called the "instance")\. You can match against the title, instance name (default), class name, or role (the WM_WINDOW_ROLE property) by explicitly specifying it\. You can also specify multiple matches, which must ALL match for the properties to be applied\. If a count is supplied in curly brackets at the end of the app line, then the entry will only match at most that many at any time (default is to match all matching windows)\. Settings associated with an [app] line will not be applied to transient windows\. [transient] may be used instead to match them\.
+Property can be one of the following tags:
+.sp
+o name \- the name of the window (the first field of WM_CLASS) o class \- class of the window (the second field of WM_CLASS) o title \- title of the window (the WM_NAME property) o role \- role of the window (the WM_WINDOW_ROLE property)
+.sp
+You can find out the value for these fields for a particular window by running xprop(1)\. The window title should be used only as a last resort, since it often changes after the window opens\. Each \fIvalue\fR can be a string or a regular expression\. All values are case sensitive\.
+.sp
+You can specify multiple properties, which must ALL match for the settings to be applied\. If a count is supplied in curly brackets at the end of the app line, then the entry will only match at most that many at any time (default is to match all matching windows)\. Settings associated with an [app] line will not be applied to transient windows\. [transient] may be used instead to match them\.
 .sp
 .sp
 .RS 4
 .nf
 # match a standard xterm
-[app] (xterm)
+[app] (name=xterm)
 # match an xterm started like: xterm \-name myshell
-[app] (myshell)
-# match any one Firefox window (the instance name is "Gecko")
-[app] (class=Firefox\-bin) {1}
+[app] (name=myshell)
 # match the gaim buddy list window
 [app] (role=buddy_list)
 # match an rdesktop window to a particular host
 [app] (title=rdesktop \- hostname\.*)
-# match gaim IRC windows
-[app] (gaim) (title=#\.*)
+# match pidgin IRC windows
+[app] (pidgin) (title=#\.*)
 .fi
 .RE
-The following are the properties that can be defined in each [app] entry\. Each name must be enclosed in square brackets, and the value is generally in curly brackets:
+The following are the settings that can be defined in each [app] entry\. Each name must be enclosed in square brackets, and the value is generally in curly brackets:
 .sp
 .sp
 .RS 4
@@ -1244,7 +1248,7 @@ The following are the properties that can be defined in each [app] entry\. Each
 .RE
 .sp
 .RS 4
-\h'-04'\(bu\h'+03'[Position] (\fBrefspot\fR)) {X Y}: Position the application at a particular spot:
+\h'-04'\(bu\h'+03'[Position] (\fBrefspot\fR) {X Y}: Position the application at a particular spot:
 .sp
 .RS 4
 \h'-04'\(bu\h'+03'TOPLEFT
@@ -1309,7 +1313,7 @@ is positioned (X,Y) pixels from the lower right of the screen\.
 .RE
 .sp
 .RS 4
-\h'-04'\(bu\h'+03'[FocusHidden] {yes|no}: Hides the app from the window cycling list used Next/PrevWindow key bindings\.
+\h'-04'\(bu\h'+03'[FocusHidden] {yes|no}: Hides the app from the window cycling list used by Next/PrevWindow key bindings\.
 .RE
 .sp
 .RS 4
@@ -1356,56 +1360,40 @@ enabled, focus enabled\.
 .RE
 The apps file also allows you to specify applications that should be started only valid option is (screen=NN), where NN is the screen number on which the command should be run\.
 .sp
-Finally, you can set windows to group together by using the `apps\' file\. This can be achieved with regular expressions using:
-.sp
-.sp
-.RS 4
-.nf
-[app] (property=expr) \.\.\. {number}
-.fi
-.RE
-Property can be one of the following tags:
-.sp
-o name \- the name of the window (the first field of WM_CLASS) o class \- class of the window (the second field of WM_CLASS) o title \- title of the window ( WM_NAME property) o role \- role of the window (the WM_WINDOW_ROLE property)
-.sp
-If no `property\' is specified, the name property is assumed\. You can find out the value for these fields for a particular window by running xprop(1)\.
-.sp
-You can also place [group] tag around several [app] tags, with an [end] tag to indicate the end of the group\. If you place (workspace) after the [group] tag, a new window will only get grouped with other windows on the current workspace\. You can also specify dimensions, positions, etc\. for the group as for normal app entries\. Here is a short example of an `apps\' file:
+Finally, you can set windows to group together by using the `apps\' file\. Just place a [group] tag around several [app] tags, with an [end] tag to indicate the end of the group\. If you place (workspace) after the [group] tag, a new window will only get grouped with other windows on the current workspace\. You can also specify dimensions, positions, etc\. for the group as for normal app entries\. Here is a short example of an `apps\' file:
 .sp
 .sp
 .RS 4
 .nf
     [startup] {xterm}
     # match anything ending with term, up to 2 instances
-    [app] (\.*[tT]erm) {2}
-    # match anything with `gaim\' in the title
-    [app] (title=\.*gaim\.*)
-    [app] (kate)
-        [Dimensions]  {1022 747}
-        [Position]    (WINCENTER) {0 0}
-        [Close]       {yes}
+    [app] (name=\.*[tT]erm) {2}
+      [Workspace]   {1}
     [end]
-    [app] (konqueror)
-        [Workspace]   {1}
-        [Dimensions]  {1006 749}
-        [Position]    {16 0}
-        [Jump]        {yes}
+    [app] (name=kate)
+      [Dimensions]  {1022 747}
+      [Position]    (WINCENTER) {0 0}
+      [Close]       {yes}
+    [end]
+    [app] (name=konqueror)
+      [Workspace]   {1}
+      [Dimensions]  {1006 749}
+      [Position]    {16 0}
+      [Jump]        {yes}
     [end]
     # start all aterms without decorations
-    [app] (aterm)
-        [Deco]        {NONE}
+    [app] (name=aterm)
+      [Deco]        {NONE}
     [end]
     # a group with the gimp dock and toolbox
     # appears on layer 4 (bottom)
     [group]
-      [app] (gimp) (role=gimp\-dock)
-      [app] (gimp) (role=gimp\-toolbox)
-        [Layer] {4}
+     [app] (name=gimp) (role=gimp\-dock)
+     [app] (name=gimp) (role=gimp\-toolbox)
+      [Layer]       {4}
     [end]
 .fi
 .RE
-Parameters in the `apps\' file are case\-sensitive\. Application names are taken from the first X window WM_CLASS attribute by default (WM_NAME = title, WM_WINDOW_ROLE = role)\. You can see this attribute by using the xprop command\. Take care when using regular expressions\. If you are not familiar with regular expressions you can disable this feature by specifying \-\-disable\-regexp during configure\. Plain strings will then be matched\.
-.sp
 .SH "THE SLIT"
 The slit is a special fluxbox window frame that can contain dockable applications, e\.g\. \fIbbtools\fR or \fIwmapps\fR\.
 .sp
diff --git a/doc/asciidoc/fluxbox.txt b/doc/asciidoc/fluxbox.txt
index e357fd4..7ca1456 100644
--- a/doc/asciidoc/fluxbox.txt
+++ b/doc/asciidoc/fluxbox.txt
@@ -1115,28 +1115,33 @@ of fluxbox can be controlled by the overlay file, see fluxstyle(1).
 APPLICATIONS
 ------------
 It is possible to force an application to always have the same dimensions,
-position, and other settings when it is first launched. This is done using
-either the window-menu `Remember...' submenu, or by directly using the
-~/.fluxbox/apps file. Be careful about editing the apps file while fluxbox is
-running. Your changes may be overwritten. Following is a listing of the valid
-entries for the `apps' file.  The `Remember...' submenu has entries for most
-options that store the current state in the `apps' file for future use.
+position, and other settings when it is first launched. The easiest way to do
+this is to use the `Remember...' submenu of the window menu, which can usually
+be opened with a right click on the titlebar. More advanced features require
+manually editing the ~/.fluxbox/apps file, where these settings are saved.
 
-The format of a line in the `apps' file is:
+The format of a section in the `apps' file is:
 
 ....................................
-[app] (app-name) {count - optional}
-    [Property1]  {value1}
-    [Property2]  {value2}
+[app] (Property='value') ... {count - optional}
+    [Setting1]  {value1}
+    [Setting2]  {value2}
     ...
 [end]
 ....................................
 
-Each app-name can be a string, or a regular expression. By default the name
-is matched against a window's WM_CLASS property (the first string in it, called
-the "instance"). You can match against the title, instance name (default), class
-name, or role (the WM_WINDOW_ROLE property) by explicitly specifying it. You can
-also specify multiple matches, which must ALL match for the properties to be
+Property can be one of the following tags:
+
+o   name - the name of the window (the first field of WM_CLASS)
+o   class - class of the window (the second field of WM_CLASS)
+o   title - title of the window (the WM_NAME property)
+o   role - role of the window (the WM_WINDOW_ROLE property)
+
+You can find out the value for these fields for a particular window by running
+xprop(1). The window title should be used only as a last resort, since it often changes after the window opens. Each 'value' can be a string or a regular
+expression. All values are case sensitive.
+
+You can specify multiple properties, which must ALL match for the settings to be
 applied. If a count is supplied in curly brackets at the end of the app line,
 then the entry will only match at most that many at any time (default is to
 match all matching windows). Settings associated with an [app] line will not be
@@ -1144,22 +1149,20 @@ applied to transient windows. [transient] may be used instead to match them.
 
 ...................................................................
 # match a standard xterm
-[app] (xterm)
+[app] (name=xterm)
 # match an xterm started like: xterm -name myshell
-[app] (myshell)
-# match any one Firefox window (the instance name is "Gecko")
-[app] (class=Firefox-bin) {1}
+[app] (name=myshell)
 # match the gaim buddy list window
 [app] (role=buddy_list)
 # match an rdesktop window to a particular host
 [app] (title=rdesktop - hostname.*)
-# match gaim IRC windows
-[app] (gaim) (title=#.*)
+# match pidgin IRC windows
+[app] (pidgin) (title=#.*)
 ...................................................................
 
-The following are the properties that can be defined in each [app] entry.
-Each name must be enclosed in square brackets, and the value is generally in
-curly brackets:
+The following are the settings that can be defined in each [app] entry. Each
+name must be enclosed in square brackets, and the value is generally in curly
+brackets:
 
 - [Workspace] \{0-N\}:
     Forces the application to open on the workspace specified.  Workspaces are
@@ -1168,7 +1171,7 @@ curly brackets:
 - [Dimensions] \{Width Height\}:
     Open the application with the specified width and height, in pixels.
 
-- [Position] (*refspot*)) {X Y}:
+- [Position] (*refspot*) {X Y}:
     Position the application at a particular spot:
     +
         * TOPLEFT
@@ -1202,7 +1205,7 @@ curly brackets:
     Hides the app from the icon bar
 
 - [FocusHidden] {yes|no}:
-    Hides the app from the window cycling list used Next/PrevWindow key
+    Hides the app from the window cycling list used by Next/PrevWindow key
     bindings.
 
 - [Hidden] {yes|no}:
@@ -1245,64 +1248,43 @@ on fluxbox startup using [startup] (options) {command} lines. Currently, the
 only valid option is (screen=NN), where NN is the screen number on which the
 command should be run.
 
-Finally, you can set windows to group together by using the `apps' file.  This
-can be achieved with regular expressions using:
-
-     [app] (property=expr) ... {number}
-
-Property can be one of the following tags:
-
-o   name - the name of the window (the first field of WM_CLASS)
-o   class - class of the window (the second field of WM_CLASS)
-o   title - title of the window ( WM_NAME property)
-o   role - role of the window (the WM_WINDOW_ROLE property)
-
-If no `property' is specified, the name property is assumed. You can find out
-the value for these fields for a particular window by running xprop(1).
-
-You can also place [group] tag around several [app] tags, with an [end] tag to
-indicate the end of the group. If you place (workspace) after the [group] tag, a
-new window will only get grouped with other windows on the current workspace.
-You can also specify dimensions, positions, etc. for the group as for normal app
-entries. Here is a short example of an `apps' file:
+Finally, you can set windows to group together by using the `apps' file. Just
+place a [group] tag around several [app] tags, with an [end] tag to indicate the
+end of the group. If you place (workspace) after the [group] tag, a new window
+will only get grouped with other windows on the current workspace. You can also
+specify dimensions, positions, etc. for the group as for normal app entries.
+Here is a short example of an `apps' file:
 
 .........................................................
     [startup] {xterm}
     # match anything ending with term, up to 2 instances
-    [app] (.*[tT]erm) {2}
-    # match anything with `gaim' in the title
-    [app] (title=.*gaim.*)
-    [app] (kate)
-        [Dimensions]  {1022 747}
-        [Position]    (WINCENTER) {0 0}
-        [Close]       {yes}
+    [app] (name=.*[tT]erm) {2}
+      [Workspace]   {1}
     [end]
-    [app] (konqueror)
-        [Workspace]   {1}
-        [Dimensions]  {1006 749}
-        [Position]    {16 0}
-        [Jump]        {yes}
+    [app] (name=kate)
+      [Dimensions]  {1022 747}
+      [Position]    (WINCENTER) {0 0}
+      [Close]       {yes}
+    [end]
+    [app] (name=konqueror)
+      [Workspace]   {1}
+      [Dimensions]  {1006 749}
+      [Position]    {16 0}
+      [Jump]        {yes}
     [end]
     # start all aterms without decorations
-    [app] (aterm)
-        [Deco]        {NONE}
+    [app] (name=aterm)
+      [Deco]        {NONE}
     [end]
     # a group with the gimp dock and toolbox
     # appears on layer 4 (bottom)
     [group]
-      [app] (gimp) (role=gimp-dock)
-      [app] (gimp) (role=gimp-toolbox)
-        [Layer] {4}
+     [app] (name=gimp) (role=gimp-dock)
+     [app] (name=gimp) (role=gimp-toolbox)
+      [Layer]       {4}
     [end]
 .........................................................
 
-Parameters in the `apps' file are case-sensitive. Application names are taken
-from the first X window WM_CLASS attribute by default (WM_NAME = title,
-WM_WINDOW_ROLE = role). You can see this attribute by using the xprop
-command. Take care when using regular expressions. If you are not familiar with
-regular expressions you can disable this feature by specifying --disable-regexp
-during configure. Plain strings will then be matched.
-
 THE SLIT
 --------
 The slit is a special fluxbox window frame that can contain dockable
diff --git a/doc/fluxbox-keys.5 b/doc/fluxbox-keys.5
index 6509712..61fa49a 100644
--- a/doc/fluxbox-keys.5
+++ b/doc/fluxbox-keys.5
@@ -252,7 +252,8 @@ window is visible on all workspaces\.
 .RS 4
 Sets which window decorations will be shown\.
 \fIdecor\fR
-has the same format as the `[Deco]\' parameter in the apps file\. See man fluxbox section APPLICATION SETTINGS for more info\.
+has the same format as the `\fI parameter in the apps file\. See `man fluxbox\fR
+section APPLICATIONS for more info\.
 .RE
 .PP
 \fBToggleDecor\fR
@@ -775,8 +776,6 @@ Many of the more advanced commands take a \fIpattern\fR argument, which allows y
 .sp
 ([\fIpropertyname\fR[!]=]\fIregexp\fR) \&...
 .sp
-That is, one or more match definitions, followed by an optional limit on the number of windows to match\.
-.sp
 Match definitions are enclosed in parentheses \fB(\fR\&...\fB)\fR, and if no \fIpropertyname\fR is given then \fBName\fR is assumed\. The \fIregexp\fR can contain any regular expression, or the special value \fB[current]\fR, which matches the corresponding value of the currently focused window\. See \fIregex(7)\fR for more information on acceptable regular expressions\.
 .sp
 You can use \fB=\fR to test for equality or \fB!=\fR to test for inequality\.
diff --git a/doc/fluxbox.1.in b/doc/fluxbox.1.in
index 4d14f71..0272673 100644
--- a/doc/fluxbox.1.in
+++ b/doc/fluxbox.1.in
@@ -1,11 +1,11 @@
 .\"     Title: fluxbox
 .\"    Author: 
 .\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
-.\"      Date: 08/19/2008
+.\"      Date: 08/20/2008
 .\"    Manual: 
 .\"    Source: 
 .\"
-.TH "FLUXBOX" "1" "08/19/2008" "" ""
+.TH "FLUXBOX" "1" "08/20/2008" "" ""
 .\" disable hyphenation
 .nh
 .\" disable justification (adjust text to left margin only)
@@ -1199,40 +1199,44 @@ The default installation of fluxbox provides some of these style files\. See flu
 In addition to the style file, the overlay file, whose location is specified by session\.screen0\.styleOverlay (default: ~/\.fluxbox/overlay ) can be used to set style resources that override all styles\. For more information about which parts of fluxbox can be controlled by the overlay file, see fluxstyle(1)\.
 .sp
 .SH "APPLICATIONS"
-It is possible to force an application to always have the same dimensions, position, and other settings when it is first launched\. This is done using either the window\-menu `Remember\&...\fI submenu, or by directly using the ~/\.fluxbox/apps file\. Be careful about editing the apps file while fluxbox is running\. Your changes may be overwritten\. Following is a listing of the valid entries for the `apps\fR file\. The `Remember\&...\fI submenu has entries for most options that store the current state in the `apps\fR file for future use\.
+It is possible to force an application to always have the same dimensions, position, and other settings when it is first launched\. The easiest way to do this is to use the `Remember\&...\' submenu of the window menu, which can usually be opened with a right click on the titlebar\. More advanced features require manually editing the ~/\.fluxbox/apps file, where these settings are saved\.
 .sp
-The format of a line in the `apps\' file is:
+The format of a section in the `apps\' file is:
 .sp
 .sp
 .RS 4
 .nf
-[app] (app\-name) {count \- optional}
-    [Property1]  {value1}
-    [Property2]  {value2}
+[app] (Property=\'value\') \.\.\. {count \- optional}
+    [Setting1]  {value1}
+    [Setting2]  {value2}
     \.\.\.
 [end]
 .fi
 .RE
-Each app\-name can be a string, or a regular expression\. By default the name is matched against a window\'s WM_CLASS property (the first string in it, called the "instance")\. You can match against the title, instance name (default), class name, or role (the WM_WINDOW_ROLE property) by explicitly specifying it\. You can also specify multiple matches, which must ALL match for the properties to be applied\. If a count is supplied in curly brackets at the end of the app line, then the entry will only match at most that many at any time (default is to match all matching windows)\. Settings associated with an [app] line will not be applied to transient windows\. [transient] may be used instead to match them\.
+Property can be one of the following tags:
+.sp
+o name \- the name of the window (the first field of WM_CLASS) o class \- class of the window (the second field of WM_CLASS) o title \- title of the window (the WM_NAME property) o role \- role of the window (the WM_WINDOW_ROLE property)
+.sp
+You can find out the value for these fields for a particular window by running xprop(1)\. The window title should be used only as a last resort, since it often changes after the window opens\. Each \fIvalue\fR can be a string or a regular expression\. All values are case sensitive\.
+.sp
+You can specify multiple properties, which must ALL match for the settings to be applied\. If a count is supplied in curly brackets at the end of the app line, then the entry will only match at most that many at any time (default is to match all matching windows)\. Settings associated with an [app] line will not be applied to transient windows\. [transient] may be used instead to match them\.
 .sp
 .sp
 .RS 4
 .nf
 # match a standard xterm
-[app] (xterm)
+[app] (name=xterm)
 # match an xterm started like: xterm \-name myshell
-[app] (myshell)
-# match any one Firefox window (the instance name is "Gecko")
-[app] (class=Firefox\-bin) {1}
+[app] (name=myshell)
 # match the gaim buddy list window
 [app] (role=buddy_list)
 # match an rdesktop window to a particular host
 [app] (title=rdesktop \- hostname\.*)
-# match gaim IRC windows
-[app] (gaim) (title=#\.*)
+# match pidgin IRC windows
+[app] (pidgin) (title=#\.*)
 .fi
 .RE
-The following are the properties that can be defined in each [app] entry\. Each name must be enclosed in square brackets, and the value is generally in curly brackets:
+The following are the settings that can be defined in each [app] entry\. Each name must be enclosed in square brackets, and the value is generally in curly brackets:
 .sp
 .sp
 .RS 4
@@ -1244,7 +1248,7 @@ The following are the properties that can be defined in each [app] entry\. Each
 .RE
 .sp
 .RS 4
-\h'-04'\(bu\h'+03'[Position] (\fBrefspot\fR)) {X Y}: Position the application at a particular spot:
+\h'-04'\(bu\h'+03'[Position] (\fBrefspot\fR) {X Y}: Position the application at a particular spot:
 .sp
 .RS 4
 \h'-04'\(bu\h'+03'TOPLEFT
@@ -1309,7 +1313,7 @@ is positioned (X,Y) pixels from the lower right of the screen\.
 .RE
 .sp
 .RS 4
-\h'-04'\(bu\h'+03'[FocusHidden] {yes|no}: Hides the app from the window cycling list used Next/PrevWindow key bindings\.
+\h'-04'\(bu\h'+03'[FocusHidden] {yes|no}: Hides the app from the window cycling list used by Next/PrevWindow key bindings\.
 .RE
 .sp
 .RS 4
@@ -1356,56 +1360,40 @@ enabled, focus enabled\.
 .RE
 The apps file also allows you to specify applications that should be started only valid option is (screen=NN), where NN is the screen number on which the command should be run\.
 .sp
-Finally, you can set windows to group together by using the `apps\' file\. This can be achieved with regular expressions using:
-.sp
-.sp
-.RS 4
-.nf
-[app] (property=expr) \.\.\. {number}
-.fi
-.RE
-Property can be one of the following tags:
-.sp
-o name \- the name of the window (the first field of WM_CLASS) o class \- class of the window (the second field of WM_CLASS) o title \- title of the window ( WM_NAME property) o role \- role of the window (the WM_WINDOW_ROLE property)
-.sp
-If no `property\' is specified, the name property is assumed\. You can find out the value for these fields for a particular window by running xprop(1)\.
-.sp
-You can also place [group] tag around several [app] tags, with an [end] tag to indicate the end of the group\. If you place (workspace) after the [group] tag, a new window will only get grouped with other windows on the current workspace\. You can also specify dimensions, positions, etc\. for the group as for normal app entries\. Here is a short example of an `apps\' file:
+Finally, you can set windows to group together by using the `apps\' file\. Just place a [group] tag around several [app] tags, with an [end] tag to indicate the end of the group\. If you place (workspace) after the [group] tag, a new window will only get grouped with other windows on the current workspace\. You can also specify dimensions, positions, etc\. for the group as for normal app entries\. Here is a short example of an `apps\' file:
 .sp
 .sp
 .RS 4
 .nf
     [startup] {xterm}
     # match anything ending with term, up to 2 instances
-    [app] (\.*[tT]erm) {2}
-    # match anything with `gaim\' in the title
-    [app] (title=\.*gaim\.*)
-    [app] (kate)
-        [Dimensions]  {1022 747}
-        [Position]    (WINCENTER) {0 0}
-        [Close]       {yes}
+    [app] (name=\.*[tT]erm) {2}
+      [Workspace]   {1}
     [end]
-    [app] (konqueror)
-        [Workspace]   {1}
-        [Dimensions]  {1006 749}
-        [Position]    {16 0}
-        [Jump]        {yes}
+    [app] (name=kate)
+      [Dimensions]  {1022 747}
+      [Position]    (WINCENTER) {0 0}
+      [Close]       {yes}
+    [end]
+    [app] (name=konqueror)
+      [Workspace]   {1}
+      [Dimensions]  {1006 749}
+      [Position]    {16 0}
+      [Jump]        {yes}
     [end]
     # start all aterms without decorations
-    [app] (aterm)
-        [Deco]        {NONE}
+    [app] (name=aterm)
+      [Deco]        {NONE}
     [end]
     # a group with the gimp dock and toolbox
     # appears on layer 4 (bottom)
     [group]
-      [app] (gimp) (role=gimp\-dock)
-      [app] (gimp) (role=gimp\-toolbox)
-        [Layer] {4}
+     [app] (name=gimp) (role=gimp\-dock)
+     [app] (name=gimp) (role=gimp\-toolbox)
+      [Layer]       {4}
     [end]
 .fi
 .RE
-Parameters in the `apps\' file are case\-sensitive\. Application names are taken from the first X window WM_CLASS attribute by default (WM_NAME = title, WM_WINDOW_ROLE = role)\. You can see this attribute by using the xprop command\. Take care when using regular expressions\. If you are not familiar with regular expressions you can disable this feature by specifying \-\-disable\-regexp during configure\. Plain strings will then be matched\.
-.sp
 .SH "THE SLIT"
 The slit is a special fluxbox window frame that can contain dockable applications, e\.g\. \fIbbtools\fR or \fIwmapps\fR\.
 .sp
diff --git a/src/ClientPattern.hh b/src/ClientPattern.hh
index 611adeb..4e25cb5 100644
--- a/src/ClientPattern.hh
+++ b/src/ClientPattern.hh
@@ -74,6 +74,8 @@ public:
     bool addTerm(const std::string &str, WinProperty prop, bool negate = false);
 
     void addMatch() { ++m_nummatches; }
+    void removeMatch() { --m_nummatches; }
+    void resetMatches() { m_nummatches = 0; }
 
     // whether this pattern has identical matching criteria
     bool operator ==(const ClientPattern &pat) const;
diff --git a/src/FocusableList.cc b/src/FocusableList.cc
index d15e10a..98492b8 100644
--- a/src/FocusableList.cc
+++ b/src/FocusableList.cc
@@ -156,10 +156,12 @@ void FocusableList::checkUpdate(Focusable &win) {
     if (contains(win)) {
         if (!m_pat->match(win)) {
             m_list.remove(&win);
+            m_pat->removeMatch();
             m_removesig.notify(&win);
         }
     } else if (m_pat->match(win)) {
         insertFromParent(win);
+        m_pat->addMatch();
         m_addsig.notify(&win);
     }
 }
@@ -194,9 +196,10 @@ void FocusableList::addMatching() {
     const Focusables list = m_parent->clientList();
     Focusables::const_iterator it = list.begin(), it_end = list.end();
     for (; it != it_end; ++it) {
-        if (m_pat->match(**it))
+        if (m_pat->match(**it)) {
             pushBack(**it);
-        else // we still want to watch it, in case it changes to match
+            m_pat->addMatch();
+        } else // we still want to watch it, in case it changes to match
             attachSignals(**it);
     }
 }
@@ -279,6 +282,7 @@ void FocusableList::reset() {
         detachSignals(*m_list.back());
         m_list.pop_back();
     }
+    m_pat->resetMatches();
     if (m_parent)
         addMatching();
     m_resetsig.notify(0);
diff --git a/src/Remember.cc b/src/Remember.cc
index 43437f4..a1f5d62 100644
--- a/src/Remember.cc
+++ b/src/Remember.cc
@@ -1373,6 +1373,16 @@ void Remember::updateClientClose(WinClient &winclient) {
     checkReload(); // reload if it's changed
     Application *app = find(winclient);
 
+    if (app) {
+        Patterns::iterator it = m_pats->begin();
+        for (; it != m_pats->end(); it++) {
+            if (it->second == app) {
+                it->first->removeMatch();
+                break;
+            }
+        }
+    }
+
     if (app && (app->save_on_close_remember && app->save_on_close)) {
 
         for (int attrib = 0; attrib < REM_LASTATTRIB; attrib++) {
diff --git a/src/WorkspaceCmd.cc b/src/WorkspaceCmd.cc
index 592b34b..41c7832 100644
--- a/src/WorkspaceCmd.cc
+++ b/src/WorkspaceCmd.cc
@@ -69,8 +69,7 @@ FbTk::Command<void> *WindowListCmd::parse(const string &command, const string &a
     if (tokens.size() > 1) {
         FocusableList::parseArgs(tokens[1], opts, pat);
 
-        filter = FbTk::CommandParser<bool>::instance().parse(pat,
-                                                                     trusted);
+        filter = FbTk::CommandParser<bool>::instance().parse(pat, trusted);
     }
 
     return new WindowListCmd(FbTk::RefCount<FbTk::Command<void> >(cmd), opts,