RegTab — Regular Table Language

RegTab matches tables the way RegEx matches text. RTL (Regular Table Language) is the pattern DSL for extracting structured records from arbitrarily-shaped tables, developed by the RegTab project.

RTL patterns describe the layout of a table (subtables, rows, cells), constrain cell content, and specify how matched cells are interpreted into a record set. This extension works with any RegTab implementation — jRegTab (Java), pyRegTab (Python) — and with standalone .rtl files that are not tied to a host runtime at all.

// Airline on-time performance: header row + repeated data rows
[ [] [VAL: 'AIRLINE'->AVP]+ ]
[ [VAL: 'AIRPORT'->AVP] [VAL: (COL,ROW,CL)->REC, 'ND'->AVP ' ' VAL: 'MON'->AVP]+ ]+

Installation

Until the Marketplace listing is live, install from a VSIX file:

1. Download the package for your platform from Releases:

   Your system	File
   Windows x64	regtab-rtl-<version>-win32-x64.vsix
   Windows ARM	regtab-rtl-<version>-win32-arm64.vsix
   Linux x64 / ARM64	…-linux-x64.vsix / …-linux-arm64.vsix
   Alpine Linux	…-alpine-x64.vsix
   macOS Intel / Apple Silicon	…-darwin-x64.vsix / …-darwin-arm64.vsix
   anything else	…-universal.vsix (highlighting/snippets only — no bundled language server; point rtl.server.path at your own rtl-lsp build for the full feature set)

2. Install it — either from the terminal:

   code --install-extension regtab-rtl-<version>-<platform>.vsix
   

   or from the UI: Extensions panel → ⋯ menu (top right) → Install from VSIX… → pick the file. Reload the window afterwards.

A VSIX installed this way does not auto-update — install a newer VSIX over it to upgrade (settings and state are kept).

Features

• Compile diagnostics as you type — powered by rtl-lsp, a standalone native language server built on the RegTab Rust core. Errors are underlined at the exact source position with the compiler's message — in .rtl files and inside RTL string literals in Python/Java (escapes and text-block indentation are mapped back correctly). EXT('…') predicates are never reported as unbound while editing standalone files (they bind to the host runtime only at run time). Platform-specific builds bundle the server; on other platforms point rtl.server.path at your own binary, or use the extension with highlighting only.

  

• Live match preview — run the pattern against a CSV fixture: each matched cell-derived item's segment is colored by role (VAL / ATTR / AUX) inside the cell text, the extracted recordset is shown alongside, and the preview re-runs as you edit. Fixtures bind via a // fixture: directive (paths resolve against the file's directory; ${workspaceFolder} is substituted), the RTL: Select Fixture… command, or the rtl.fixtures.input glob template for whole directories of patterns (with snippet-style ${basename/regex/replacement/} transforms for host files whose names don't literally match the fixture layout). Works on .rtl files and on RTL string literals in Python/Java (RtlCompiler.compile, @RtlSource, language=RTL markers) via a CodeLens on each literal.

• Expected-result diff — bind an expected CSV to a fixture (an // expected: directive or the rtl.fixtures.expected template) and the preview turns red/green: it diffs the extracted recordset against the expected rows (unordered multiset by default; header and row-order policies are settings) and lists the missing and extra records.

  

• Test Explorer — every pattern × fixture pair with an expected result appears in VS Code's Testing view: run a whole directory of patterns and get pass/fail with the diff on failures — regression checks for pattern catalogs, no Python or JDK required.

  

• Canonical form on demand — the RTL: Show Canonical Form command opens a read-only view of the normalized pattern (inherited actions pushed down to atoms): see what the compiler actually understood, or compare two differently written patterns for equivalence. It is intentionally not a formatter — canonicalization drops comments and layout, so your source is never touched.

• Hover reference on every RTL keyword — constraint semantics, action effects, extractor behavior — generated from the normative RTL reference.

• Context-aware completion — actions after ->, extractors after =, declared $fragments, known #'tags', settings inside <…>.

• $fragment navigation — go to definition, find references, rename, and an Outline view of fragments, subtables and rows.

• Syntax highlighting for .rtl files — keywords, actions, providers, extractors, fragments ($NAME), tags (#'…'), strings, comments, quantifiers.

• RTL inside Python strings — literals passed to RtlCompiler.compile("…") (single-line, triple-quoted, and raw strings) are highlighted as RTL.

• RTL inside Java strings — RtlCompiler.compile("…"), the @RtlSource("…") annotation, Java 15+ text blocks ("""…"""), and literals marked with /* language=RTL */.

• Snippets for frequently used combinations: ST*->REC, (SC{n}, SR)->REC(n), ^COL->AVP, ('LABEL')->AVP, CL->JOIN(0), -AV->PREFIX(', '), table and fragment skeletons, settings, conditional cells.

• Editor basics — bracket matching and auto-closing for [] {} () <>, // line comments.

No Python, JDK, or other runtime is required — the extension is fully self-contained.

Embedded RTL at a glance

Highlighting, diagnostics, and the match preview also work on RTL string literals inside host-language code:

Python

from pyregtab import RtlCompiler

pattern = RtlCompiler.compile("""
[ [ATTR]+ ]
[ [VAL : ST*->REC]+ ]+
""")

Java

@RtlSource("""
    [ [ATTR]+ ]
    [ [VAL : ST*->REC]+ ]+
    """)
String pattern;

var atp = RtlCompiler.compile("[ [VAL: 'LABEL'->AVP] ]+");

(TextMate limitation: the opening quote must be on the same line as RtlCompiler.compile( / @RtlSource(.)

Documentation

• Binding fixtures and expected results — the // fixture: / // expected: directives, the rtl.fixtures.* templates with name transforms, input↔expected pairing, comparison semantics, and how the Test Explorer discovers pattern × fixture pairs.
• FAQ and behavior notes — why there is no formatter, permissive EXT('…') handling, embedded-literal limitations, running your own rtl-lsp, troubleshooting.
• RTL reference — the language itself: constraints, actions, providers, extractors. The in-editor hover documentation is generated from this document.

Roadmap

• Excel fixtures in the preview (cell styles that CSV cannot carry).
• Semantic highlighting refinements on top of the TextMate grammar.

Grammar version

Highlighting mirrors the normative RTL grammar RTL.g4 from jRegTab 0.4.1 (RTL tokens are case-insensitive). Any change to the normative grammar must be accompanied by a matching tmLanguage update in this repository — CI enforces keyword-coverage sync.

Related projects

• jRegTab — Java implementation of RegTab.
• pyRegTab — Python implementation of RegTab (Rust core).

License

MIT