yeray/gobyexample
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use stateful regexes to better handle formatting

Browse Source
This commit is contained in:
Blake Bourque 2021-02-26 22:42:41 -05:00
parent 495f65d884
commit 4544abab6d
1 changed files with 22 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
tools/generate.go
View File

@ -354,12 +354,28 @@ var SimpleShellOutputLexer = chroma.MustNewLexer(
},
chroma.Rules{
"root": {
// first capture group is generic prompt [capture $]
// second capture group is text [capture command and newline]
// third capture group is output [capture everything else until next $]
{`(\$)(.*$\n)([^\$]*)`, chroma.ByGroups(chroma.GenericPrompt, chroma.Text, chroma.GenericOutput), nil}, //BB-gp
// everything else is just regular text
{`\n|\w`, chroma.Text, nil},
// $ or > triggers the start of prompt formatting
{`^\$`, chroma.GenericPrompt, chroma.Push("prompt")},
{`^>`, chroma.GenericPrompt, chroma.Push("prompt")},
// empty lines are just text
{`^$\n`, chroma.Text, nil},
// otherwise its all output
{`[^\n]+$\n?`, chroma.GenericOutput, nil},
},
"prompt": {
// when we find newline, do output formatting rules
{`\n`, chroma.Text, chroma.Push("output")},
// otherwise its all text
{`[^\n]+$`, chroma.Text, nil},
},
"output": {
// sometimes there isn't output so we go right back to prompt
{`^\$`, chroma.GenericPrompt, chroma.Pop(1)},
{`^>`, chroma.GenericPrompt, chroma.Pop(1)},
// otherwise its all output
{`[^\n]+$\n?`, chroma.GenericOutput, nil},
},
},
)