summaryrefslogtreecommitdiff
path: root/Content-Filters.md
diff options
context:
space:
mode:
authorsupahgreg <supahgreg@users.noreply.github.com>2025-10-05 19:59:55 +0000
committersupahgreg <supahgreg@users.noreply.github.com>2025-10-05 19:59:55 +0000
commit54771ac70bd4516d566d558318f46253919ff5c4 (patch)
treeb5725a36575945d00acbb63dcc13444b1faaff33 /Content-Filters.md
parent987e283677bde3d3f5926655a4673fb38961d08b (diff)
Switch to GitHub format for alerts/notifications (part 2).
Diffstat (limited to 'Content-Filters.md')
-rw-r--r--Content-Filters.md27
1 files changed, 12 insertions, 15 deletions
diff --git a/Content-Filters.md b/Content-Filters.md
index b1020c1..6694e8c 100644
--- a/Content-Filters.md
+++ b/Content-Filters.md
@@ -9,11 +9,10 @@ Matching is case-insensitive,
[PCRE](http://php.net/manual/en/reference.pcre.pattern.syntax.php) pattern
syntax is used.
-[!NOTE]
-
- Filter test dialog may not give entirely accurate results, especially for
- complex filters. It is suggested to test filters using ``Feed debugger`` (hotkey `f D`) if you
- feel that some filter is somehow misfiring on a specific feed.
+> [!NOTE]
+> Filter test dialog may not give entirely accurate results, especially for
+> complex filters. It is suggested to test filters using ``Feed debugger`` (hotkey `f D`) if you
+> feel that some filter is somehow misfiring on a specific feed.
### Load order
@@ -41,19 +40,17 @@ expressions.
Filter matching is performed during feed processing.
-[!NOTE]
-
- Some actions may be applied only when the article is initially imported from the
- feed. Other actions may be applied every time article is seen in the originating
- feed. It is suggested to only rely on filters applying to articles imported
- after the filter had been created - they will not retroactively apply to your
- article database.
+> [!NOTE]
+> Some actions may be applied only when the article is initially imported from the
+> feed. Other actions may be applied every time article is seen in the originating
+> feed. It is suggested to only rely on filters applying to articles imported
+> after the filter had been created - they will not retroactively apply to your
+> article database.
Several actions are available:
-[!WARNING]
-
- Filters may not apply actions conditionally based on previous filters. All actions for an article are applied together, once.
+> [!WARNING]
+> Filters may not apply actions conditionally based on previous filters. All actions for an article are applied together, once.
1. ``Delete article`` - do not import article from the feed, does not
actually delete anything from the database