summaryrefslogtreecommitdiff
path: root/pygments/lexers
Commit message (Collapse)AuthorAgeFilesLines
* all: remove "u" string prefix (#1536)Georg Brandl2020-09-0828-1168/+1165
| | | | | | | | | | | * all: remove "u" string prefix * util: remove unirange Since Python 3.3, all builds are wide unicode compatible. * unistring: remove support for narrow-unicode builds which stopped being relevant with Python 3.3
* fennel: fixup string regexGeorg Brandl2020-09-071-1/+1
|
* Avoid catastrophic backtracking.Phil Hagelberg2020-09-071-1/+1
| | | | as advised in https://github.com/pygments/pygments/pull/1535/files/f581f2892154e8e4ed673ab940abf8af43ebe66b#r484028618
* Add support for # as lambda shorthand.Phil Hagelberg2020-09-071-0/+3
|
* Remove old python-2-style strings.Phil Hagelberg2020-09-071-17/+17
|
* Update Fennel keywords to catch up to version 0.6.0.Phil Hagelberg2020-09-071-10/+14
| | | | | | Remove support for single-quoted strings. Update fennelview example to latest version of library.
* all: revert changes of [a-zA-Z0-9_] to \wGeorg Brandl2020-09-0713-51/+52
| | | | ... which is not equivalent in Unicode mode
* Update mapfilesGeorg Brandl2020-09-061-2/+2
|
* all: use argumentless super()Georg Brandl2020-09-0612-151/+81
|
* Add comment.Matthäus G. Chajdas2020-09-061-0/+3
| | | | Add a quick reminder that Javascript doesn't need integers.
* Overhaul Javascript numeric literals (#1534)Kurt McKee2020-09-061-5/+8
| | | | | | | | | | | | | | | | | | | | | | * Rename the "Javascript" tests to reflect that they are for CoffeeScript This change also modifies the module docstring to reflect the file's purpose. * Overhaul the Javascript numeric literal parsing Fixes #307 This patch contains the following changes: * Adds 50+ unit tests for Javascript numeric literals * Forces ASCII numbers for float literals (so, now reject `.୪`) * Adds support for Javascript's BigInt notation (`100n`) * Adds support for leading-zero-only octal notation (`0777`) * Adds support for scientific notation with no significand (`1e10`) Numeric literal parsing is based on information at: * https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types * https://developer.mozilla.org/en-US/docs/Web/JavaScript/Data_structures
* Simplify regex.Matthäus G. Chajdas2020-09-061-1/+1
|
* Overhaul the MySQL lexer (#1527)Kurt McKee2020-09-062-56/+1435
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Overhaul the MySQL lexer Fixes #975, #1063, #1453 Changes include: Documentation ------------- * Note in the lexer docstring that Oracle MySQL is the target syntax. MariaDB syntax is not a target (though there is significant overlap). Unit tests ---------- * Add 140 unit tests for MySQL. Literals -------- * Hexadecimal/binary/date/time/timestamp literals are supported. * Integer mantissas are supported for scientific notation. * In-string escapes are now tokenized properly. * Support the "unknown" constant. Comments -------- * Optimizer hints are now supported, and keywords are recognized and tokenized as preprocessor instructions. * Remove nested multi-line comment support, which is no longer supported in MySQL. Variables --------- * Support the '@' prefix for variable names. * Lift restrictions on characters in unquoted variable names. (MySQL does not impose a restriction on lead characters.) * Support single/double/backtick-quoted variable names, including escapes. * Support the '@@' prefix for system variable names. * Support '?' as a variable so people can demonstrate prepared statements. Keywords -------- * Keyword / data type / function are now in a separate, auto-updating file. * Support 25 additional data types (including spatial and JSON types). * Support 460 additional MySQL keywords. * Support 372 MySQL functions. Explicit function support resolves a bug that causes non-function items to be treated as functions simply because they have a trailing opening parenthesis. * Support exceptions for the 'SET' keyword, which is both a datatype and a keyword depending on context. Schema object names ------------------- * Support Unicode in MySQL schema object names. * Support parsing of backtick-quoted schema object name escapes. (Escapes do not produce a distinct token type at this time.) Operators --------- * Remove non-operator characters from the list of operators. * Remove non-punctuation characters from the list of punctuation. * Cleanup items based on feedback * Remove an unnecessary optional newline lookahead for single-line comments
* all: use yield from (#1537)Georg Brandl2020-09-0622-126/+74
|
* all: fixup some file headersGeorg Brandl2020-09-068-52/+50
|
* all: fixup remaining regexlint warningsGeorg Brandl2020-09-0645-332/+338
|
* angular2: fix missing bygroups() assignmentGeorg Brandl2020-09-061-2/+2
|
* Merge pull request #1530 from btashton/arm-gasGeorg Brandl2020-09-061-1/+1
|\ | | | | Add support for ARM constant notation in GAS lexer
| * Add support for ARM constant notation in GAS lexerBrennan Ashton2020-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GNU supports ARM syntax which uses notation like #1 for constants. Currently this is handled like a comment which is incorrect. Take the case of: ldr r0, [r1, #0] Right now the #0] would be treated like a comment and looks very poor. Was referenced in issue #627 Signed-off-by: Brennan Ashton <bashton@brennanashton.com>
* | Add lexer for PsySH console for PHP (#1438)Ben Ramsey2020-09-042-4/+58
|/ | | | | This lexer is based on the PythonConsoleLexer and provides the ability to highlight console input and output for PsySH, a developer console and REPL for PHP. See https://psysh.org.
* more explicitly define escape sequencies in JsonLexer (fix #1065) (#1528)Nick Gerner2020-08-311-2/+2
| | | | | * more explicitly define escape sequencies in JsonLexer (fix #1065) * adding test coverage for #1065
* 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.
* Fix cmake header (#1491)Thomas Aglassinger2020-08-231-1/+6
| | | | | | | | | * Fixed guessing of CMake by header. * Version number can have multiple digits. * Tabs are handled as white space. * Trailing comments are ignored. * Cleaned up regex to detect CMake header.
* Add lexer for Pointless (#1494)Avery N. Nortonsmith2020-08-232-0/+71
| | | | | | | | | | | | | | | | | | | * add lexer for pointless * lexer docstring formatting * added link to languages doc * update authors * update version * added double string * added upval keyword * simplify ptls example code * rename doubleString -> multiString
* Fix #1502.Matthäus G. Chajdas2020-08-221-4/+5
| | | | | Single-quoted strings were handled differently in the Ruby lexer compared to double-quoted strings, leading to catastrophic backtracking.
* Update copyright year (fixes #1514.)Matthäus G. Chajdas2020-08-22157-157/+157
|
* Merge pull request #1480 from ↵Matthäus G. Chajdas2020-08-221-3/+4
|\ | | | | | | | | Noordsestern/Noordsestern-robotframework-tasks-table [Robot Framework] Add syntax for tasks
| * typoNoordsestern2020-06-151-1/+1
| |
| * adding *task* to settings sectionNoordsestern2020-06-151-3/+3
| |
| * add new tables *tasks* and *task*Noordsestern2020-06-151-0/+1
| | | | | | available since Robot Framework 3.1 (January 2019)
* | Added BARE schema lexer (#1488)Martijn Braam2020-08-222-0/+101
| |
* | Mark 'syntax' as a keyword in the protobuf lexer. (#1505)Benjamin Peterson2020-08-221-1/+1
| |
* | Manually merge PR#1497.Matthäus G. Chajdas2020-08-221-3/+2
| | | | | | | | | | This is a manual merge as we don't want to pull in the documentation change as part of this fix for a cleaner history.
* | Update PostgreSQL builtins (#1513)Kurt McKee2020-08-221-16/+73
| | | | | | | | | | | | | | | | | | | | | | | | * Update the Postgres auto-update code Postgres source code locations and structure have changed a little. Also, now it works on Windows and sorts all keywords. * Update the PostgreSQL builtins Note that LC_COLLATE and LCCTYPE are removed from the keywords list. * Update AUTHORS
* | Add a PromQL lexer (#1506)Pablo SEMINARIO2020-08-192-0/+190
| | | | | | Including tests and an example.promql file.
* | Update for Csound 6.15.0 (#1509)Nate Whetsell2020-08-172-10/+43
| | | | | | | | | | * Update for Csound 6.15.0 * Update comment
* | Add async and await keywords (#1507)Marius Hegele2020-08-171-1/+1
| |
* | APL lexer: Include latest APL primitives (#1503)Bubbler-42020-08-051-2/+2
| |
* | Add Systemverilog Queue support #1496 (#1504)Kristof Mariën2020-08-051-1/+1
| | | | | | Co-authored-by: Kristof Marien <kristof.marien@nokia.com>
* | Added '*.markdown' file extension to 'markdown' lexer (#1476)Konstantin Podsvirov2020-08-021-1/+1
| | | | | | Some people use the full name of the markup.
* | Fix Arrow lexer module docstring (#1499)Ken2020-07-301-1/+1
| | | | | | oops...
* | Improve Markdown lexer (#1495)Leistungsabfall2020-07-211-21/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add support for Setext-style headings in Markdown * Improve inline code detection in Markdown * Add support for indented code blocks in Markdown * Improve italics & bold detection in Markdown * Simplify italics & bold regexes in Markdown * Add warning about possible unrecognized internal tags in Markdown * Improve striktethrough detection in Markdown * Small bugfix in Markdown * Small bugfix in Markdown * Small refactoring in Markdown
* | Add support for PowerShell Remoting sessions (#1398)Geert Smelt2020-06-301-1/+1
| | | | | | | | | | | | | | | | | | | | | | * Add support for PowerShell Remoting sessions * Add test case for PowerShell Remoting sessions * Make whitespace after prompt optional * Fix test case containing backslashes * Add test case for local PowerShell sessions
* | Add Arrow lexer (#1481)Ken2020-06-212-0/+116
|/ | | | | | | * Add Arrow lexer * Pass tests: raw string for regex * Make requested changes
* Improve SystemVerilog class/endclass lexer rules (#1471)Chris Drake2020-06-061-8/+10
| | | | | | | | | | | The class looks like: class class_identifier [#(param_decls)] [extends class_identifier #(params)]; ... endclass [: class_identifier] Using the same Java convention of Keyword.Declaration and Name.Class. Add a test_systemverilog_classes unit test to test_hdl.
* add Singularity lexer (#1285)Georg Brandl2020-06-012-2/+36
| | | Co-authored-by: Bryton Hall <email@bryton.io>
* Nasm: Update register syntax for 64-bit (#1465)Jonas Bushart2020-06-011-1/+1
| | | | | | | x86_64 has 8 registers r8-r15. The current syntax only accepts them with a trailing letter. The letter is used to indicate the register size. However, r8 is also a valid register, for a 64 bit wide register. For reference on the register names see https://www.cs.uaf.edu/2017/fall/cs301/reference/x86_64.html
* SystemVerilog keyword/operator improvements (#1464)Chris Drake2020-06-011-14/+20
| | | | | | | | | | | | | | | | | | | | | | | | | * Move SystemVerilog type keywords Put them next to the generic keywords list. * Change a couple SystemVerilog keywords to operators The 'inside' and 'dist' keywords are described as operators in the SystemVerilog standard, below unary increment/decrement, and above concatenation in precedence. See 1800-2017 tables 11-1 and 11-2 for a list of operators. This matches the description of pygemnts Operator.Word token: "For any operator that is a word (e.g. not)." * Add a SystemVerilog operators unit test Copy/paste the contents of 1800-2017 Table 11-2, and see what the SV lexer chops it up into. I made lots of comments for potential improvements. Some operators, such as '[' and '.' are being labeled as punctuation. Also, multi-character operators such as '<<<=' are being split up into multiple, single-character tokens, eg '<' '<' '<' '='.
* Add GDScript lexer (#1457)Paweł Fertyk2020-06-013-0/+379
| | | | | | | | | | | | | | | | | | | | | * Added GDScript lexer * Fix regular expressions in GDScript lexer * Update GDScript lexer with the current version from Godot docs * Add tests for GDScript lexer * Update authors * Add an example file for GDScript * Implement analyze_text for GAP and GDScript * Fix example file name in tests * Update license Co-authored-by: Daniel J. Ramirez <djrmuv@gmail.com>