Adds 'ClientPatternTest' command

ClientPatterns might be tricky to get right. Instead of fiddling around in
either the keys-file or the apps-file and restarting fluxbox to see if the
changes had any effect / matched the right windows, 'ClientPatternTest' and
the fluxbox-remote should make this easier:

    $> fluxbox-remote "clientpatterntest (title=.*vim*)"

This causes fluxbox to store the list of matched windows in the
_FLUXBOX_ACTION_RESULT property onto the rootwindow. This property might
then be read by:

    $> xprop -root _FLUXBOX_ACTION_RESULT

or

    $> fluxbox-remote result

The format of the list is:

    win_id \t title_of_window \n

win_id is '-1' when fluxbox wasn't able to parse the given ClientPattern.
win_id is '0' when there are no windows matching the given ClientPattern.

1 files changed, 1 insertions, 0 deletions

diff --git a/src/ClientPattern.hh b/src/ClientPattern.hh
index a5b7206..358977a 100644
--- a/src/ClientPattern.hh
+++ b/src/ClientPattern.hh
@@ -89,6 +89,7 @@ public:
      * the column of the error is stored in m_matchlimit
      */
     int error() const { return m_terms.empty() ? 1 : 0; }
+    int error_col() const { return m_matchlimit; }
 
     static FbTk::FbString getProperty(WinProperty prop, const Focusable &client);