| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
| |
This commit adds a new url field to a lexer, which can be used to link
to the language website, instead of relying on having the link in either
languages.rst or the docstring of the lexer. Additionally, it changes the
languages.rst file to auto-generate the list of lexers from the actual
source code, using the provided URL.
|
|\
| |
| |
| | |
of https://github.com/blu-base/pygments into blu-base-lexers_ijkl
|
| | |
|
| |
| |
| |
| |
| | |
Highlighting as Keyword.Declaration is consistent with the
RacketLexer.
|
| |
| |
| |
| |
| |
| | |
Previously, #; awaited an S-expression but could not cope with a
simple datum like a number literal. While at it, also support R6RS
brackets for S-expressions.
|
| |
| |
| |
| |
| |
| |
| | |
This enriches the space of recognized builtins.
Note that this also fixes the space after a builtin being included in
the token.
|
| |
| |
| |
| |
| | |
Many number literals were not recognized previously, such as
fractions, infinities, hex and complex literals.
|
| |
| |
| |
| |
| | |
Move string parsing to a dedicated state so it can recognize string escapes.
Add support for various kinds of escapes.
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
|
|
|
|
| |
Treat true/false/nil as constants.
Also separate out declarations from other special forms and macros.
|
|
|
|
|
| |
* uniformize aliases order
* LighttpdConfLexer: add lighttpd.conf filename
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pyupgrade is a tool to automatically upgrade syntax for newer versions
of the Python language.
The project has been Python 3 only since
35544e2fc6eed0ce4a27ec7285aac71ff0ddc473, allowing for several cleanups:
- Remove unnecessary "-*- coding: utf-8 -*-" cookie. Python 3 reads all
source files as utf-8 by default.
- Replace IOError/EnvironmentError with OSError. Python 3 unified these
exceptions. The old names are aliases only.
- Use the Python 3 shorter super() syntax.
- Remove "utf8" argument form encode/decode. In Python 3, this value is
the default.
- Remove "r" from open() calls. In Python 3, this value is the default.
- Remove u prefix from Unicode strings. In Python 3, all strings are
Unicode.
- Replace io.open() with builtin open(). In Python 3, these functions
are functionally equivalent.
Co-authored-by: Matthäus G. Chajdas <Anteru@users.noreply.github.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
| |
as advised in https://github.com/pygments/pygments/pull/1535/files/f581f2892154e8e4ed673ab940abf8af43ebe66b#r484028618
|
| |
|
| |
|
|
|
|
|
|
| |
Remove support for single-quoted strings.
Update fennelview example to latest version of library.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Run the pyupgrade tool across the project to use modern language
features.
- Use set literals
- Use dict comprehension
- Remove unnecessary numeric indexes in format string
- Remove unnecessary extra parentheses
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Fix external links in RdLexer and NewLispLexer
Approved-by: James Martindale <atlassian@jkmartindale.com>
|
| |\
| | |
| | |
| | | |
Hy lexer should accept colons inside identifiers
|
| | |
| | |
| | |
| | |
| | | |
Colons inside identifiers are completely legal in this Lisp dialect. Also
prevents the lexer from catching on Python literals when lexing REPL output.
|
| |\ \ |
|
| | | | |
|
| | |/
| | |
| | |
| | | |
lexer files
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
Add support for the Fennel programming language
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a pretty straightforward language in the lisp family with a
small number of special forms. Since Fennel runs on the Lua runtime,
the list of builtins is the same as that of Lua, so it might be
possible to re-use the definition from the Lua lexer, but since I
don't know Python I couldn't figure out how that would work; maybe
someone else could add that.
|
| |/
| |
| |
| |
| |
| | |
So we return instead. Fix needed for Python 3.7.
Fixes https://bitbucket.org/birkenfeld/pygments-main/issues/1457
|
|/ |
|
| |
|
|
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.
|