fix: color triggers now work inside 'only pass matches' trigger groups

[vadi2]

Brief overview of PR changes/additions

• A color-pattern trigger nested under an "only pass matches" (filter) parent could never fire: the filter ran children with no buffer line to read colors from
• The real line number is now passed through, and the color scan is limited to the parent's matched text so filter semantics hold; top-level color triggers behave exactly as before

Motivation for adding to Mudlet

Filter chains are the standard way to scope triggers, and color patterns silently did nothing inside them.

Other info (issues closed, discussion etc)

Fixes #8198
Known limitation: children of multiline filter parents still can't use color patterns (a multiline match spans several lines, so no single line applies).

Test case: create a perl-regex trigger ^(hello world)$ with "only pass matches" ticked, nest a color trigger (foreground ANSI yellow) under it with echo("CHILD FIRED\n"), then lua feedTriggers("\27[33mhello world\27[0m\n") - the child fires. Covered by the new ColorTriggerFilterChildTest (ctest).

trimmed.mp4

[add-deployment-links]

Hey there! Thanks for helping Mudlet improve. 🌟

Test versions

You can directly test the changes here:

• linux: https://make.mudlet.org/snapshots/327c3c/Mudlet-4.22.0-testing-pr9442-b044fff5-linux-x64.AppImage.tar (commit b044fff)
• osx intel: https://make.mudlet.org/snapshots/633ba9/Mudlet-4.22.0-testing-pr9442-b044fff5-x86_64.dmg (commit b044fff)
• osx arm: https://make.mudlet.org/snapshots/79a53a/Mudlet-4.22.0-testing-pr9442-b044fff5-arm64.dmg (commit b044fff)
• windows 64 bit: https://make.mudlet.org/snapshots/45a284/Mudlet-4.22.0-testing-pr9442-b044fff5-windows-64.zip (commit b044fff)

No need to install anything - just unzip and run.
Let us know if it works well, and if it doesn't, please give details.

[greptile-apps]

_{Reviews (1): Last reviewed commit: "Fix: color trigger under a filter parent..." | Re-trigger Greptile}