| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| | |
Highlight %a in Python3Lexer
Approved-by: PurpleMyst <purplemyst2017@gmail.com>
|
| |\
| | |
| | |
| | |
| | |
| | | |
Fix issue #1389: Markdown lexer bug
Approved-by: Anteru <bitbucket@ca.sh13.net>
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Updated the documentation as well to make clear which Python versions are
officially supported.
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | | |
Update Dockerfile lexer
Approved-by: m m <marnitto@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add Dockerfiles new keyword in the lexer
Improve lexer to parse json arrays on specific commands
Handle line breaks as a bash syntax
|
| | |\ \
| | | | |
| | | | |
| | | | | |
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.
|
| | |\ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add HLSL lexer
Approved-by: Anteru <bitbucket@ca.sh13.net>
|
| | | |\ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
PEP 479: Raising StopIteration from a generator is now an error
Approved-by: Anteru <bitbucket@ca.sh13.net>
|
| | | | |\ \
| | | | | |/
| | | | |/| |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | |/ /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
So we return instead. Fix needed for Python 3.7.
Fixes https://bitbucket.org/birkenfeld/pygments-main/issues/1457
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
- Also added a snippet to the example file where a string shows up (uncommon in HLSL).
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes the bug reported in #1389, where the markdown lexer will not issue a
token for the closing code fence.
Issue: #1389
|
|/ / / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/|
| | | |
When no output file is specified, use the "terminal256" formatter by default if TERM contains "256".
|
| | | |
|
| |\ \
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
Custom Lexer/Formatter File Loading
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | | |
update LassoLexer
|
| | | | | | |
|
| | | |\ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
Image Formatter: Mac-specific lookup for fonts (fixes #868)
|
| | | | |\ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
add 'nginx.conf' to NginxConfLexer
|
| | | | | |\ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Revised version of ncl.py
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
add some punctuation
|