Keyboard Summary

         O  :Other‐Filter (upper case)
             You will be prompted to establish a case sensitive filter.

         o  :Other‐Filter (lower case)
             You will be prompted to establish a filter that ignores case when matching.

        ^O  :Show‐Active‐Filters (Ctrl key + ‘o’)
             This can serve as a reminder of which filters are active in the ‘current’ window.  A summary will be shown on the message line until you press the <Enter> key.

         =  :Reset‐Filtering in current window
             This clears all of your selection criteria in the ‘current’ window.  It also has additional impact so please see topic 4a. GLOBAL Commands.

         +  :Reset‐Filtering in all windows
             This clears the selection criteria in all windows, assuming you are in alternate-display mode.  As with the ‘=’ interactive command, it too has additional consequences so you might wish to see topic 5b. COMMANDS
             for Windows.

       Input Requirements

          When prompted for selection criteria, the data you provide must take one of two forms.  There are 3 required pieces of information, with a 4th as optional.  These examples use spaces  for  clarity  but  your  input
          generally would not.
                  #1           #2  #3              ( required )
                  Field-Name   ?   include-if-value
               !  Field-Name   ?   exclude-if-value
               #4                                  ( optional )

          Items #1, #3 and #4 should be self-explanatory.  Item #2 represents both a required delimiter and the operator which must be one of either equality (‘=’) or relation (‘<’ or ‘>’).

          The ‘=’ equality operator requires only a partial match and that can reduce your ‘if-value’ input requirements.  The ‘>’ or ‘<’ relational operators always employ string comparisons, even with numeric fields.  They
          are designed to work with a field’s default justification and with homogeneous data.  When some field’s numeric amounts have been subjected to scaling while others have not, that data is no longer homogeneous.

          If  you  establish  a  relational  filter  and you have changed the default Numeric or Character justification, that filter is likely to fail.  When a relational filter is applied to a memory field and you have not
          changed the scaling, it may produce misleading results.  This happens, for example, because ‘100.0m’ (MiB) would appear greater than ‘1.000g’ (GiB) when compared as strings.

          If your filtered results appear suspect, simply altering justification or scaling may yet achieve the desired objective.  See the ‘j’, ‘J’ and ‘e’ interactive commands for additional information.

       Potential Problems

          These GROUP filters could produce the exact same results or the second one might not display anything at all, just a blank task window.
               GROUP=root        ( only the same results when )
               GROUP=ROOT        ( invoked via lower case ‘o’ )

          Either of these RES filters might yield inconsistent and/or misleading results, depending on the current memory scaling factor.  Or both filters could produce the exact same results.
               RES>9999          ( only the same results when )
               !RES<10000        ( memory scaling is at ‘KiB’ )

          This nMin filter illustrates a problem unique to scalable fields.  This particular field can display a maximum of 4 digits, beyond which values are automatically scaled to KiB or above.  So  while  amounts  greater
          than 9999 exist, they will appear as 2.6m, 197k, etc.
               nMin>9999         ( always a blank task window )

       Potential Solutions

          These  examples  illustrate  how Other Filtering can be creatively applied to achieve almost any desired result.  Single quotes are sometimes shown to delimit the spaces which are part of a filter or to represent a
          request for