| 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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| | |
|
| | |
|
| |
|
|
|
| |
It's no longer 0 to resolve an ambiguity with the TypeScript lexer -- different
file endings are used.
|
| | |
|
| |
|
|
|
| |
.typoscript is used for TypoScript files, removing the ambiguity with
TypeScript.
|
| | |
|
| | |
|
| |\
| |
| |
| | |
Implement guessing and resolution between TypeScript and TypoScript.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These values would trigger problems when guessing content without a filename,
and really aren't needed. They've been removed, allowing the standard behavior
to take place.
On top of this, the regex for TypeScript has been slightly altered to include
a whitespace match after "export" to be within the group for the "export"
text.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new TypoScript lexer was taking precedence over TypeScript, which share
the same file extension. This meant that any previously-working TypeScript
source files would be misidentified and highlighted incorrectly. This was due
to the lack of a guesser for TypeScript, and TypoScript having a naturally
higher priority.
This change balances things a bit between the lexers. TypoScript now has an
explicitly-higher priority than TypeScript, both for the file extension and
defaults when guessing content, as it has less we can rely on in terms of
content. TypeScript has a lower priority, but has an analyse_text() method
that checks for common symbols in code, giving it a better chance of matching
for actual TypeScript source files.
TypeScript also gains an additional file extension, *.tsx. Ideally, this would
have its own lexer that understood inline JSX syntax, but giving general
TypeScript syntax highlighting for these files is a step in the right
direction.
|
| | | |
|
| |
|
|
| |
Source: https://github.com/Tuurlijk/Pygments-TypoScript-Lexer
|
| | |
|
| | |
|
|
|
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.
|
