summaryrefslogtreecommitdiff
path: root/pygments/lexers/textfmts.py
Commit message (Collapse)AuthorAgeFilesLines
* all: use yield from (#1537)Georg Brandl2020-09-061-2/+1
|
* all: fixup remaining regexlint warningsGeorg Brandl2020-09-061-13/+13
|
* Make group optionalrugk2020-08-231-2/+2
|
* Fix HttpLexer to allow 2.0rugk2020-08-231-2/+2
| | | | | According to [RFC7540 (section 3.5)](https://tools.ietf.org/html/rfc7540#section-3.5), if I interpret it correctly, it actually even _has to_ start with `2.0` and not `2`. As HTTP/3 is also defined there, I have not looked into how that has to be used/started.
* Update copyright year (fixes #1514.)Matthäus G. Chajdas2020-08-221-1/+1
|
* Make HttpLexer compatible with RFC 7230 (section 3.1.2). Specifically this ↵Joshua Huber2020-05-181-1/+1
| | | | addresses for the case where only a numeric HTTP status code is returned (eg. 200) and no textual reason phrase (eg. OK). Strictly according to RFC 7230, the whitespace just after the status code number is NOT optional, and in fact Tomcat 8.5 behaves this way, emiting status lines like "HTTP/1.1 200 \n" (note the whitespace after the 200). (#1432)
* make regexes consistentGeorg Brandl2019-12-091-1/+1
|
* dmesg lexer refinements:Georg Brandl2019-12-091-2/+51
| | | | | | * move to textfmts.py where other logfiles are * fix detection of dmesg -x (heuristic "unknown" state must be last) * change styles for debug/warn lines
* Make the optional reason-phrase regexp group non-capturing.Jakub Roztocil2019-12-031-3/+3
|
* Parse HTTP status-line even when reason-phrase not included.Jakub Roztocil2019-12-021-2/+2
| | | | Background: https://github.com/jakubroztocil/httpie/issues/811
* Added support for HTTP protocol versions 2 and 3ocket88882019-11-301-2/+2
|
* Add Notmuch lexerDaniel Santana2019-11-261-3/+88
|
* Fixup all headers and some more minor problems.2.4.2Georg Brandl2019-05-281-1/+1
|
* Fix more instances of invalid string escapesGeorg Brandl2018-11-281-5/+5
| | | | Also, raise on warnings from Pygments only.
* Copyright update.Georg Brandl2017-01-221-1/+1
|
* Add support for partials and path segments for Handlebars.Christian Hammond2016-11-041-0/+297
This introduces support for some missing features to the Handlebars lexer: Partials and path segments. Partials mostly appeared to work before, but the `>` in `{{> ... }}` would appear as a syntax error, as could other components of the partial. This change introduces support for: * Standard partials: `{{> partialName}}` * Partials with parameters: `{{> partialName varname="value"}}` * Ddynamic partials: `{{> (partialFunc)}}` * Ddynamic partials with lookups: `{{> (lookup ../path "partialName")}}` * Partial blocks: `{{> @partial-block}}` * Inline partials: `{{#*inline}}..{{/inline}}` It also introduces support for path segments, which can reference content in the current context or in a parent context. For instance, `this.name`, `this/name`, `./name`, `../name`, `this/name`, etc. These are all now tracked as variables.