roulette/vendor/github.com/alecthomas/chroma/v2/lexers
Seednode 57e5b7dff2 Updated transitive dependencies 2023-12-04 11:40:53 -06:00
..
embedded Updated transitive dependencies 2023-12-04 11:40:53 -06:00
README.md Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
caddyfile.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
cl.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
dns.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
emacs.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
genshi.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
go.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
haxe.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
html.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
http.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
lexers.go Updated transitive dependencies 2023-10-29 21:49:49 -05:00
markdown.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
mysql.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
php.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
raku.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
rst.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
svelte.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
typoscript.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00
zed.go Add syntax highlighting for code 2023-09-14 17:37:22 -05:00

README.md

Chroma lexers

All lexers in Chroma should now be defined in XML unless they require custom code.

Lexer tests

The tests in this directory feed a known input testdata/<name>.actual into the parser for <name> and check that its output matches <name>.expected.

It is also possible to perform several tests on a same parser <name>, by placing know inputs *.actual into a directory testdata/<name>/.

Running the tests

Run the tests as normal:

go test ./lexers

Update existing tests

When you add a new test data file (*.actual), you need to regenerate all tests. That's how Chroma creates the *.expected test file based on the corresponding lexer.

To regenerate all tests, type in your terminal:

RECORD=true go test ./lexers

This first sets the RECORD environment variable to true. Then it runs go test on the ./lexers directory of the Chroma project.

(That environment variable tells Chroma it needs to output test data. After running go test ./lexers you can remove or reset that variable.)

Windows users

Windows users will find that the RECORD=true go test ./lexers command fails in both the standard command prompt terminal and in PowerShell.

Instead we have to perform both steps separately:

  • Set the RECORD environment variable to true.
    • In the regular command prompt window, the set command sets an environment variable for the current session: set RECORD=true. See this page for more.
    • In PowerShell, you can use the $env:RECORD = 'true' command for that. See this article for more.
    • You can also make a persistent environment variable by hand in the Windows computer settings. See this article for how.
  • When the environment variable is set, run go test ./lexers.

Chroma will now regenerate the test files and print its results to the console window.