Git with a cup of tea, painless self-hosted git service Mirror for internal git.with.parts use https://git.with.parts
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
gitea/vendor/github.com/alecthomas/chroma/lexers
6543 86e2789960
Vendor Update (#16121)
3 years ago
..
a Vendor Update (#16121) 3 years ago
b Vendor Update (#16121) 3 years ago
c Vendor Update (#16121) 3 years ago
circular Vendor Update (#16121) 3 years ago
d Vendor Update (#16121) 3 years ago
e Vendor Update (#16121) 3 years ago
f Vendor Update (#16121) 3 years ago
g Vendor Update (#16121) 3 years ago
h Vendor Update (#16121) 3 years ago
i Vendor Update (#16121) 3 years ago
internal Vendor Update (#16121) 3 years ago
j Vendor Update (#16121) 3 years ago
k Vendor Update (#16121) 3 years ago
l Vendor Update (#16121) 3 years ago
m Vendor Update (#16121) 3 years ago
n Vendor Update (#16121) 3 years ago
o Vendor Update (#16121) 3 years ago
p Vendor Update (#16121) 3 years ago
q Vendor Update (#16121) 3 years ago
r Vendor Update (#16121) 3 years ago
s Vendor Update (#16121) 3 years ago
t Vendor Update (#16121) 3 years ago
v Vendor Update (#16121) 3 years ago
w Vendor Update (#16121) 3 years ago
x Vendor Update (#16121) 3 years ago
y Vendor Update (#16121) 3 years ago
z Vendor Update (#16121) 3 years ago
README.md Server-side syntax highlighting for all code (#12047) 4 years ago
lexers.go update chroma to v0.8.0 (#12337) 4 years ago

README.md

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>.exported.

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 tests ./lexers.

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