summaryrefslogtreecommitdiff
path: root/pygments
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | Add "friendly grayscale" theme (#1273)Oliver Kopp2021-12-282-0/+76
| | | | | | | | | | | | | | | Fixes https://github.com/pygments/pygments/issues/1040
* | | | | Improve objdump-nasm lexer (#1981)Pwilke2021-12-281-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Update asm lexer for --no-show-raw-insn * Update asm lexer for #-style comments in Nasm Co-authored-by: Pierre Wilke <pierre.wilke@centralesupelec.fr>
* | | | | Merge pull request #1804 from Cl00e9ment/masterMatthäus G. Chajdas2021-12-281-1/+1
|\ \ \ \ \ | | | | | | | | | | | | ABNF rulename can be 1 character wide
| * | | | | fixed typoClément Saccoccio2021-05-131-1/+1
| | | | | |
* | | | | | Refine the One Dark theme a bit for consistency with other popular projects ↵ranelpadon2021-12-281-15/+15
| |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | (Atom, Vim, Alacritty, etc) using the same theme (#1979) * Refine the One Dark a bit, for consistency with other projects using One Dark. * Revert the unintentional change in Operator's bold style.
* | | | | Lexer for new language Elpi (#1894)Enrico Tassi2021-12-122-0/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * lexers: add Elpi * test: elpi * Fix copyright * address code review
* | | | | Add missing keywords (Vernacular commands and tactics) for the Coq lexer (#1984)Kazuhiko Sakaguchi2021-12-101-9/+10
| | | | |
* | | | | Merge branch 'master' of https://github.com/dschwoerer/pygments into ↵Matthäus G. Chajdas2021-12-061-1/+2
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | dschwoerer-master
| * | | | | Add links to lines with css-line numbersDavid Bold2021-11-261-1/+2
| | | | | |
* | | | | | Clarifying some documentation (#1928)Arthur Milchior2021-12-061-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * NF: adding an example of use of simple filter @simplefilter is great, but also not very intuitive. Indeeds, the syntax seems to indicate that you define a function with four arguments while in reality you define a class whose constructor takes arbitrary keyword arguments. I believe in this case an example to show how to instantiate this filter is really necessary. Regarding simplefilter, I also believe that it could be improved in two simple ways: * accepting any method which takes lexer and stream as a filter. That would be sufficient as long as there is no option * the @simplefilter decorator could deal with `self` so that the user do not have to add it themselves. Probably not worth doing it no, as it would break compatibility with current version, but would be even simpler to use * NF: clarifying get_..._options get_bool_opt's documentation seems to indicate that the key is interpreted as a Boolean. While a quick look at the code shows clearly that the value associated to the key is what is interpreted as a Boolean. I hope I made the code clearer to any people who know python by indicating that it is essentially `.get` but with extra features * NF: clarifying Filter `filter` has already a specific behavior in general python, or for any people used to functional programing (and even if some dom processor). So indicating that a filter is not something that remove some tokens seems really useful to try to explain what is going on. * NF: adding details regarding states in lexer I found the state explanation confusing. I do know what a state machine is. However, reading the code, I first thought that there were two distinct variables: * the current state * the stack that are somehow related but distinct. Explaining that the current state is the top of the stack was lacking in my opinion. That also help explain #push. In particular that if you define in state "s" an operation whose new state is "#push", the behavior can be quite different than if the new state was "s".
* | | | | | Fix whitespace handling, update CHANGES.Matthäus G. Chajdas2021-12-061-4/+4
| | | | | |
* | | | | | Merge branch 'master' of https://github.com/chillibits/pygments into ↵Matthäus G. Chajdas2021-12-062-0/+61
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | chillibits-master
| * | | | | | Fix underliningMarc Auberer2021-12-051-1/+1
| | | | | | |
| * | | | | | Finish lexer implementation for SpiceMarc Auberer2021-12-052-54/+15
| | | | | | |
| * | | | | | Create Spice lexer fileMarc Auberer2021-12-051-0/+100
| | | | | | |
* | | | | | | Merge branch 'lexers_ef' of https://github.com/blu-base/pygments into ↵Matthäus G. Chajdas2021-12-0612-177/+217
|\ \ \ \ \ \ \ | |/ / / / / / |/| | | | | | | | | | | | | blu-base-lexers_ef
| * | | | | | Fix regex marked by regexling in felix lexerSebastian Engel2021-11-141-1/+1
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: futharkSebastian Engel2021-11-141-5/+5
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: forthSebastian Engel2021-11-141-5/+6
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: floscriptSebastian Engel2021-11-141-5/+4
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: felixSebastian Engel2021-11-141-12/+15
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: fantomSebastian Engel2021-11-141-28/+30
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: factorSebastian Engel2021-11-141-77/+101
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: ezhilSebastian Engel2021-11-141-4/+4
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: esotericSebastian Engel2021-11-141-12/+16
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: erlangSebastian Engel2021-11-141-13/+15
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: elmSebastian Engel2021-11-141-6/+9
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: eiffelSebastian Engel2021-11-141-7/+9
| | | | | | |
| * | | | | | Modernize Whitespace token in lexer: eclSebastian Engel2021-11-141-3/+3
| | | | | | |
* | | | | | | Update CHANGES, language list.Matthäus G. Chajdas2021-11-281-1/+3
| | | | | | |
* | | | | | | New lexer for Sophia contracts (#1974)Hans Svensson2021-11-282-0/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * New lexer for Sophia contracts * Whitespacee should be Text.Whitespace * Update golden files
* | | | | | | Fix checks.Matthäus G. Chajdas2021-11-272-2/+8
| | | | | | |
* | | | | | | Updates CHANGES, version info.Matthäus G. Chajdas2021-11-271-1/+1
| | | | | | |
* | | | | | | Add support for BDD features / stories (#1803)xuan2021-11-272-0/+54
| |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Create BDD.py Initialize the lexer file of BDD Add keywords of BDD * Update the 'RegexLexer' * Edit and test * Update BDD.py * Update BDD.py * Update the BddLexer file * Update the BddLexer of root tokens * edit bdd Add regular expression for tokens * edit bdd Add regular expression for tokens * add .gitignore * updata bdd.lexer * Delete bdd.py * Update the Keywords, Numbers, Punctuation token * bdd.py Assign different colors to keywords, punctuation, numbers, and variables. * Update the BddLexer file * Update bdd.py Fix the file name. * Add the detection for '@' Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com> * Update bdd.py Add detection of double quotes. Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com> * Fix the double quotes * fix the quote recognition * add comments * update the root dir * add bdd test cases * Delete .DS_Store * Delete .DS_Store * Delete .DS_Store * remove DS file * restore the gitignore file * update the bdd lexer * update the bdd lexer * update the whitespace highlight * update the whitespace highlight * refactor the bdd.py * update the punctuation * update the punctuation * update bdd token Change "." to the "\S+", Which reduce the test output file size. Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com> * Update bdd.py Reduce the new token for each space Co-authored-by: Hongyuan Yan <hongyuan.yan@student.adelaide.edu.au> Co-authored-by: OMGJL <lzhsjunkmail@gmail.com> Co-authored-by: Hongyuan Yan <54675432+kirito330824@users.noreply.github.com> Co-authored-by: Jessie2110 <71688609+Jessie2110@users.noreply.github.com> Co-authored-by: Jessie2110 <wuqiong2110@gmail.com> Co-authored-by: OMGJL <8707895+OMGJL@users.noreply.github.com>
* | | | | | Rename LilypondStyle to LilyPondStyle (#1971)Jean-Abou-Samra2021-11-242-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | It was silly from mine to call it LilypondStyle (lowercase 'p') whereas the lexer is called LilyPondLexer (uppercase 'P').
* | | | | | Fixes for LilyPond (#1968)Jean-Abou-Samra2021-11-213-25/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * LilyPond: update builtins to 2.23.4 * Doc: deduplicate LilyPond in language lists * Doc: exclude lilypond style from gallery Because it's specific to LilyPond code and doesn't give good results on Python code.
* | | | | | Fix remaining LilyPond issues.Matthäus G. Chajdas2021-11-212-4/+3
| | | | | |
* | | | | | Remove UTF-8 comment.Matthäus G. Chajdas2021-11-211-1/+0
| | | | | |
* | | | | | Various small cleanups.Matthäus G. Chajdas2021-11-214-2/+9
| | | | | |
* | | | | | Add lexer and style for LilyPond (#1845)Jean-Abou-Samra2021-11-215-16/+5007
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add lexer and style for LilyPond GNU LilyPond is a text-based music typesetter. Because its concepts are completely different from programming languages, this adds a special-purpose to highlight the special tokens. The SchemeLexer is expanded to gain the ability of detecting when one expression stops. LilyPondLexer subclasses SchemeLexer. Builtins (the most important part) are generated with a script put in external/ (as was already done for Lasso). As part of this change, the CPSALexer is made no longer to inherit from SchemeLexer. The inheritance was unused anyway. * Fixup: translators names have underscores * Fixup: avoid duplicate builtins * Fixup: update goldens * Fixup: typo * Fixup: add missing tokens to style * Fixup: update lexer comments * Fixup: Tentative style adjustments * Fixup: move test file to examplefiles/ * Fixup: miscellaneous fixes (to be finished) * Fixup: escape all braces * Fixup: use Text, not Whitespace * Fixup: fixes for lexing and style * Fixup: update goldens! * Fixup: also test alist assignments * Fixup: recognize escape sequences in strings * Fixup: use Comment.Single * Fixup: Whitespace, not Text! * Fixup: fix pitch parsing * Fixup: update comment * Fixup: remove redundant re.UNICODE
* | | | | | Update CHANGES, versionadded info.Matthäus G. Chajdas2021-11-211-1/+1
| | | | | |
* | | | | | add a lexer for .SRCINFO files (#1951)Jendrik2021-11-212-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * add a lexer for .SRCINFO files * add an example file that tests architecture dependent keys * fix module name underline
* | | | | | Don't produce two tokens per tag in Savi.Matthäus G. Chajdas2021-11-211-2/+2
| |_|_|/ / |/| | | |
* | | | | Add lexer for the Savi language. (#1863)Joe Eli McIlvain2021-11-212-0/+160
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add lexer for the Savi language. * Updates based on review comments. * Prefer Text.Whitespace token over Text token for whitespace. * Updates to Savi lexer based on changes to Rouge Savi lexer. * Add versionadded identifier to Savi lexer.
* | | | | Register the one-dark style.Matthäus G. Chajdas2021-11-211-1/+2
| | | | |
* | | | | Creating one dark style (#1924)TobiZog2021-11-211-0/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Creating one dark style * Adding copyright informations * Bugfix * Fogetting one ~
* | | | | Merge pull request #1935 from Mango0x45/masterMatthäus G. Chajdas2021-11-212-6/+41
|\ \ \ \ \ | | | | | | | | | | | | Add a lexer for the sed scripting language
| * \ \ \ \ Merge branch 'master' into masterThomas Voss2021-11-032-6/+0
| |\ \ \ \ \
| * | | | | | Remove accidental tab characterThomas Voss2021-10-311-1/+1
| | | | | | |
| * | | | | | Add a lexer for the sed scripting languageThomas Voss2021-10-312-6/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sed is a stream editing scripting language forming part of the POSIX standard. This means that sed cn be found as part of any POSIX compliant OS such as Linux, MacOS, and the BSDs. This lexer supports the complete POSIX standard for sed as well as various GNU extensions. The names 'gsed' and 'ssed' may sometimes be used as part of a file extension to refer specifically to GNU sed or Super Sed, two popular implementations of sed. The sed language is rather simple, here is a quick overview: - Comments begin with a '#' and continue to the end of the line. - Commands can be prepended with a range that selects lines. This can be either a number ([0-9]+), a '$', or a regular expression. Regular expressions can either be enclosed in '/' such as /regex/ or they can be exclosed in any other character however the opening delimiter must be escaped, for example: \@regex@. - Some commands such as 'w', 'r', and 'b' take a string as a parameter, this string extends either to the next ';' or newline. - Some commands such as 'a' can take multiline strings. - Commands can be grouped with braces ('{' and '}'). - The 'y' command takes two strings as parameters, seperated by any delimiter ('y/abc/123/' or 'y|abc|123|') - The 's' command is like the 'y' command but the fist parameter is a regular expression. Additionally it takes an optional 3rd parameter which are a sequence of flags ('s|regex|replace|flags'). I chose to add support for GNU sed extensions as it is by far the most used implementation.
View Lorry Controller Status