Monitoring Tools

Search

Regex builder parity ledger

Baseline: the official RegexBuddy manual, family list reviewed 2026-11-04. Product baseline: Monitoring Tools 1.0.8, .NET 8 System.Text.RegularExpressions.

Status words: done (implemented, with checks that drive the built app; any genuine limit is listed beside it), partial (some subfeatures work, the rest are listed), missing. Nothing is marked done from source reading alone. A complete per-topic ledger covering every manual topic is still to be written; this family ledger is the first step, not that ledger.

Count after the second 2026-11-05 pass: 13 families, 13 done, 0 partial, 0 missing (after the first pass: 9 done, 4 partial; before it: 0 done, 13 partial). Every check named below is in src/MonitoringTools/UI/SelfTest.RegexParity.cs and runs with MT_ONLY=regexparity or in the full self-test.

FamilyStatusWhat worksWhat is missing, and genuine limits
Construction and syntaxdoneRaw editing; token palette for classes, Unicode properties, subtraction, anchors (including \G), named, numbered, balancing, atomic and non-capturing groups, backreferences, conditionals, quantifiers (greedy and lazy), lookaround, inline options, comments; selection-wrapping insertion; literal escaping; all .NET options. Guided editing of a selected quantifier, character set, group, anchor (pick another), shorthand class, escape, (?#...) comment and balancing group; a conditional (condition kind: group has matched or one of the four lookaround tests; the test; the yes and no branches; Swap branches; a group test must name a group that exists). Earlier and Later buttons and a mouse drag of a tree row onto a neighbouring row, which keep the text of each part and refuse a result .NET rejects. The drag reads the window's own mouse messages, so it behaves the same for a pointer and for posted messages. Checked by regex parity tree (core rewrites, conditional read and rewrite), regex parity ui build (select a part, press the editor control, read the pattern back; a conditional is swapped, turned into a look-ahead and refused for a missing group) and a real left-button drag posted to the builder window (down, moves, up), including a click that must not move and a cross-level drop that must be refused. The same drag was also posted from a separate process on the hidden test desktop (MT_ONLY=regexdrag).Limit: recursion, subroutine calls, POSIX classes and replacement case conversion do not exist in .NET (listed as unavailable in the palette, with reasons).
Replacement constructiondoneReplacement field with group, named group, $$, $&, $+, before, after and whole-input tokens (all as insert chips); live preview; a separate replacement explanation (each $ token and literal run described; references to groups the pattern lacks flagged because .NET would copy them as plain text).Limit: replacement conditionals and case conversion do not exist in .NET, so they are shown as unavailable and cannot be offered.
Analysis and exportsdoneSyntax tree for the .NET flavour cross-checked against the real engine, with the engine's message and position when it rejects a pattern; two-way selection between tree and pattern box; brief or detailed explanations; flat token list; backtracking-risk warning; export as Markdown or HTML, which now also carries the match results (positions and groups) and a timing line with the growth run for the current sample (regex parity export).Limit: the tree is this app's parser, because .NET does not expose its internal tree. Patterns nested deeper than 150 levels give a partial tree. Match results are capped at 50 in an export. The Save dialog itself is not driven; the content is checked through the same functions the buttons call.
Flavour comparison and conversiondoneCompare view, "Other engines on this computer": the same pattern text runs in the Windows JScript engine (ECMAScript 3, through COM), the .NET Framework engine in Windows PowerShell 5.1, and Python re and Node.js (V8) when installed, each as a bounded child process or worker (6 s, pattern sent as data). Each result shows the engine's own error, match count, time and how it differs from .NET. The Code view translates a .NET pattern and replacement for Python, JavaScript and Java and names every construct it cannot translate (regex parity flavours, regex parity ui compare; Python and Node results compared with .NET on this computer, including an astral-character subject).Limit: PCRE, Perl, Ruby, Go and a Java runtime are not installed on a stock Windows computer, so those engines cannot be run offline; Java output is translated but never executed. Conversion goes from .NET to the other flavours only.
Testing and datadoneMatch and split; match list with positions; capture table; empty matches; selection in the sample; measured time; sample from the searched list; expected-outcome test cases saved with Library entries; match scope for the whole text, each line or each page (positions stay positions in the whole sample, ^ and $ act per piece); convert line breaks to LF or CRLF with a description of what the sample contains; paste from the clipboard; read a file in Auto, UTF-8, UTF-16 or Latin-1 (a byte order mark wins and is named); hexadecimal dump of the sample in the chosen encoding (regex parity sample, regex parity ui test).The Open file dialog and, on a hidden desktop with no clipboard, the clipboard read itself are not driven: the check calls the same paste and file-read functions the buttons call and says so.
DebuggerdoneDebug view: a separate instrumented backtracking interpreter with Prev, Next, Play, highlighted pattern token and text position, 100,000 step limit. It covers literals, ., classes including Unicode general categories (\p{L}, \P{Nd}, inside sets) and class subtraction ([a-z-[aeiou]], nested), anchors including \G, groups, look-ahead and look-behind (positive and negative), atomic groups, conditionals on a group (by name or number) or on a lookaround test, inline options (?imsn-imsn) and (?imsn-imsn:...) scoped as .NET scopes them, the explicit capture option, alternation, greedy and lazy repeats and backreferences. Before a trace is shown the overall match and every capture group are compared with the real .NET engine; any disagreement withholds the trace (regex parity debug for 24 inline-option, conditional, subtraction and \G cases; regex parity ui debug in the Debug view).Not traced, and reported by name: the x option, (?#...) comments, Unicode scripts and blocks, a conditional whose condition names no group (which .NET tests as an expression), right-to-left, non-backtracking, ECMAScript. Limit: it is not the .NET engine's own trace, which .NET does not expose. Only the first 4,000 characters of the subject are traced.
Benchmark and diagnosticsdoneStatic risk detection for nested quantifiers and overlapping alternation; 200 ms timeout; growth run at 1x to 16x with a verdict, off the UI thread with Cancel. New: run two patterns side by side on the same sample with matches, first difference and speed; time per top-level part of the pattern (prefix timing, so the jump between neighbours is the cost a part adds; alternation branches are timed one by one); a saved history of benchmark results (30 newest, per computer) with Use pattern (regex parity benchmark, regex parity ui benchmark).Limit: timings are short and noisy; the per-part figures are measurements of the real engine, not an internal profile of it.
Code and escapingdoneC#, PowerShell, Python, JavaScript and Java snippets for match, replace and split, with options, the 200 ms limit where the language has one, translated group syntax and replacement, and comment lines about anything that could not be translated. Every snippet comes from a template that can be edited in the Code view: placeholders {{literal}}, {{flags}}, {{replacement}}, {{timeout}}, {{notes}}; unknown placeholders are flagged; the change is saved per language and kind and can be restored. The generated Python, JavaScript and PowerShell snippets are run and their output checked (regex parity code, regex parity ui code).Limit: the Java snippet is generated but not run here (no Java runtime); JavaScript and Java have no match time limit and the snippet says so.
Saved collections and parametersdoneNamed library saved to settings, use, remove, JSON import and export (descriptions and parameters included; older files still load); expected-outcome test lines per entry; a description per entry; parameters written {{name}} in the pattern, each with a default and an editable value beside the entry, filled in by Use (an unfilled placeholder is kept and reported); collection search over name, description, pattern and parameter names in plain or regex mode (regex parity library, regex parity ui library).None known.
File and folder GREPdoneFiles view: folder, include and exclude masks, subfolders, binary and size skipping, encoding detection, cancellable search, results grouped by file with line, column and highlighted match, CSV export; replace in files with preview, two-key confirmation, timestamped backups, restore and a report of skipped or failed files. New: a regular expression over file names; saved searches; a results history (20 newest); every backup run listed and restorable, not only the newest; a click on a match opens the editor at that line for VS Code and Notepad++. Archives: zip, jar and nupkg read directly; 7z, rar, tar, gz, tgz, bz2, xz and cab unpacked by the bundled 7-Zip (rar by the full 7-Zip with 7z.dll, checked on a RAR5 built by the check) into a temporary folder, with masks and the name pattern applied to entries, a 200 MB unpack cap, and encrypted or unreadable archives listed as skipped. Binary files searched byte by byte with offset, printable view and hexadecimal of each match. Per-extension settings (encoding, skip, binary handling) saved in settings and used by every search; a forced encoding is kept by replace. Replace never writes into archives or byte-searched files and says how many it left out (regex parity files, regex parity ui files).Limit: archives inside archives are not opened. Other editors and the system default open the file without jumping to the line, and the message says so. The two-key replace dialog is checked in core (Apply, ListBackups, RestoreFolder) and through the command line, not by pressing its buttons.
Multiple regexes and historydonePer-bar recent patterns, up to 50; opt-in (default off) storing them across restarts; independent state for every bar; two patterns side by side in the Benchmark view and a saved benchmark history that keeps earlier versions of a pattern to compare with.None known.
Integration and automationdoneMonitoringTools.exe --regex: match listing, replace output, JSON, option letters, exit codes 0, 1 and 2, 200 ms per-match limit, stdin. New: --lib NAME uses a saved pattern with its options, --param name=value fills its parameters, --list-library, and --in-place writes the replacement into the named files after copying each to a timestamped backup that the Files view can restore Several patterns in one command (--pattern, repeatable, and --patterns-file), listed in text order with each pattern's number; with --replace applied in order. An automation entry: --automation (or --request FILE) takes one JSON request (match, replace, split or validate; patterns with options, names or library entries; text and files) and returns one JSON result with matches, groups, line and column (regex parity cli, run as real child processes with a throwaway data folder, MT_DATA_DIR).Limit: no COM server is registered; the JSON entry is the automation interface. Console attachment when started from a terminal without redirection is implemented but not checked.
Help, editing, preferences, layoutdoneTooltips on every token and option, keyboard shortcuts, Esc returns focus. New: a Help view with 20 short pages (each with an example that is run against the real engine), page search, "Use this example", and the page for the part of the pattern the caret or selection is in shown first. Builder preferences, kept in settings: the view it opens on, card width, card height, which views show in the tab strip, detailed explanations by default, with a reset (regex parity help, regex parity ui help). All new wording has Cantonese (language audit loop).Limit: panels cannot be rearranged or docked; the layout choices are the ones listed.

View this article's Markdown source on GitHub

Suggested articles

All Search articles