gitea-tea/vendor/github.com/alecthomas/chroma/lexers
6543 0d98cbd657 Update Vendors (#337)
* update & migrate gitea sdk (Fix Delete Tag Issue)
* upgraded github.com/AlecAivazis/survey v2.2.7 => v2.2.8
* upgraded github.com/adrg/xdg v0.2.3 => v0.3.1
* upgraded github.com/araddon/dateparse
* upgraded github.com/olekukonko/tablewriter v0.0.4 => v0.0.5
* upgraded gopkg.in/yaml.v2 v2.3.0 => v2.4.0

Reviewed-on: https://gitea.com/gitea/tea/pulls/337
Reviewed-by: Norwin <noerw@noreply.gitea.io>
Reviewed-by: khmarbaise <khmarbaise@noreply.gitea.io>
Co-authored-by: 6543 <6543@obermui.de>
Co-committed-by: 6543 <6543@obermui.de>
2021-03-05 18:06:25 +08:00
..
a Update Vendors (#337) 2021-03-05 18:06:25 +08:00
b Update Vendors (#337) 2021-03-05 18:06:25 +08:00
c Update Vendors (#337) 2021-03-05 18:06:25 +08:00
circular Update Vendors (#337) 2021-03-05 18:06:25 +08:00
d Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
e Update Vendors (#337) 2021-03-05 18:06:25 +08:00
f Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
g Update Vendors (#337) 2021-03-05 18:06:25 +08:00
h Update Vendors (#337) 2021-03-05 18:06:25 +08:00
i Update Vendors (#337) 2021-03-05 18:06:25 +08:00
internal Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
j Update Vendors (#337) 2021-03-05 18:06:25 +08:00
k Update Vendors (#337) 2021-03-05 18:06:25 +08:00
l Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
m Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
n Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
o Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
p Update Vendors (#337) 2021-03-05 18:06:25 +08:00
q Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
r Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
s Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
t Update Vendors (#337) 2021-03-05 18:06:25 +08:00
v Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
w Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
x Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
y Update Vendors (#337) 2021-03-05 18:06:25 +08:00
README.md Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
hlb.go Use glamour and termev to render/colorize content (#181) 2020-09-19 16:00:50 +00:00
lexers.go Update Vendors (#337) 2021-03-05 18:06:25 +08:00

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.