@@ -43,57 +43,6 @@ Regular expressions in filter documents use ``options`` listed in the :query:`re
4343the ``i`` and ``s`` options, pass in ``"si"`` to ``options``. The order of concatenated
4444options does not matter.
4545
46- .. list-table::
47- :header-rows: 1
48- :widths: 20 80
49-
50- * - Option
51- - Description
52-
53- * - ``i``
54- - Case insensitivity to match upper and lower cases. For an
55- example, see :ref:`regex-case-insensitive`.
56-
57- * - ``m``
58-
59- - For patterns that include anchors (i.e. ``^`` for the start,
60- ``$`` for the end), match at the beginning or end of each
61- line for strings with multiline values. Without this option,
62- these anchors match at beginning or end of the string. For an
63- example, see :ref:`regex-multiline-match`.
64-
65- If the pattern contains no anchors or if the string value has
66- no newline characters (e.g. ``\n``), the ``m`` option has no
67- effect.
68-
69- * - ``x``
70-
71- - "Extended" capability to ignore all white space characters in
72- the ``$regex`` pattern unless escaped or included in a
73- character class.
74-
75- Additionally, it ignores characters in-between and including
76- an un-escaped hash/pound (``#``) character and the next new
77- line, so that you may include comments in complicated
78- patterns. This only applies to data characters; white space
79- characters may never appear within special character
80- sequences in a pattern.
81-
82- The ``x`` option does not affect the handling of the VT
83- character (i.e. code 11).
84-
85- * - ``s``
86-
87- - Allows the dot character (i.e. ``.``) to match all
88- characters *including* newline characters. For an example,
89- see :ref:`regex-dot-new-line`.
90-
91- * - ``u``
92-
93- - Supports Unicode. This flag is accepted, but is redundant. UTF is set by
94- default in the ``$regex`` operator, making the ``u`` option
95- unnecessary.
96-
9746Regular expressions in filter documents use the following fields:
9847
9948.. list-table::
0 commit comments