gitea/vendor/github.com/alecthomas/chroma/lexers
6543 86e2789960
Vendor Update (#16121)
* update github.com/PuerkitoBio/goquery

* update github.com/alecthomas/chroma

* update github.com/blevesearch/bleve/v2

* update github.com/caddyserver/certmagic

* update github.com/go-enry/go-enry/v2

* update github.com/go-git/go-billy/v5

* update github.com/go-git/go-git/v5

* update github.com/go-redis/redis/v8

* update github.com/go-testfixtures/testfixtures/v3

* update github.com/jaytaylor/html2text

* update github.com/json-iterator/go

* update github.com/klauspost/compress

* update github.com/markbates/goth

* update github.com/mattn/go-isatty

* update github.com/mholt/archiver/v3

* update github.com/microcosm-cc/bluemonday

* update github.com/minio/minio-go/v7

* update github.com/prometheus/client_golang

* update github.com/unrolled/render

* update github.com/xanzy/go-gitlab

* update github.com/yuin/goldmark

* update github.com/yuin/goldmark-highlighting

Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2021-06-10 16:44:25 +02:00
..
a Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
b Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
c Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
circular Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
d Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
e Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
f Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
g Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
h Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
i Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
internal Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
j Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
k Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
l Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
m Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
n Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
o Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
p Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
q Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
r Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
s Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
t Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
v Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
w Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
x Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
y Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
z Vendor Update (#16121) 2021-06-10 16:44:25 +02:00
lexers.go update chroma to v0.8.0 (#12337) 2020-07-27 13:18:02 -04:00
README.md Server-side syntax highlighting for all code (#12047) 2020-07-01 00:34:03 +03:00

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.