| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix a few SystemVerilog type keywords
First, add a few missing type keywords:
chandle, const, event, string, time, type, var, void
These are most of the 'variable' types listed in 1800-2017 6.8
"Variable declarations".
Currently, this 'Keyword.Type' is not taking effect because the lexer is
finding these keywords in the 'Keyword' list above.
Remove the double declaration so we get the more specific token type.
* Change signed/unsigned to Keyword.Type
This is what the C/C++ lexer does, so it seems legit.
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
* Add a basic SystemVerilog unit test
* Fix docstring
Calling it a "complete fragment" didn't make much sense.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add explicit line continuation for Matlab session
Matlab lines can be explicitly continued with the ... syntax at the end
of a line. In the Session lexer, this requires continuing to the next
line to add more text. Otherwise, the next line is marked as output.
* The ellipses in Matlab should be a Keyword
The built-in Matlab syntax highlighter highlights ... with the same
formatting as a keyword. Everything after that on the line should be a
comment.
* Update Matlab functions and keywords from R2018a
* Fix many spaces in assignment formatted as string
In command mode, MATLAB allows mutiple space separated arguments to a
function which are interpreted as char arrays, and are formatted as
Strings. This check was also catching cases where there were multiple
spaces following an assignment or comparison operation and formatting
the rest of the line as a string. Now, if an = or operator is found, the
commandargs state is popped and control returns to the root state.
* Add tests for MATLAB formatting
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add yang lexer for issue pygments/pygments#1407
* fix copyright statement
* adjust examplefile for yang
* fix to avoid duplicate code in lexer
* add more testcases for yang lexer
* simplify yang lexer
* simplify default rule in yang lexer
* change example yang file
* add version to yang lexer
|
|
|
|
|
|
|
|
|
| |
* a filter for math symbols
This filer replaces math symbols from e.g. LaTeX and Isabelle with
corresponding unicode. It could be expanded to other math-heavy
languages.
* add "symbols" filter to basic tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Implement lexer for execline.
This commit introduces a lexer for Laurent Bercot's execline scripting language
(https://skarnet.org/software/execline) based on Pygments' existing bash lexer,
with some minor adaptations for execline's variable naming rules.
* Add versionadded note and website link to execline lexer.
* Add execline to languages.rst and example execline script
* Explicitly mark non-special characters in execline lexer as Text
* Correct execline lexer version addded
Co-authored-by: Molly Miller <sysvinit@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* A lexer for F*, an ML dialect for program verification
* Fix treatment of infix applications, e.g.
* Correct modifications
* Better lexing
* Added F* to the list of supported languages
* Add example file
* Bumped versionadded field
* Added link to language
Co-authored-by: Jonathan Protzenko <jonathan.protzenko@gmail.com>
|
|
|
|
|
|
|
|
|
| |
* Add Typographic Number Theory lexer
Originally tried to use RegexLexer, but the
structure of TNT is too rigid for it to handle.
Went with a direct parser instead.
Co-authored-by: lonetwin <steve@lonetwin.net>
|
|
|
|
| |
From the fork at https://bitbucket.org/gebner/pygments-main/src/default/
|
|
|
|
|
|
|
| |
This fixes three test failures on Windows:
* Two due to incorrect handling of : (on Windows, multiple : can
be part of a path.)
* One due to newline differences
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove Python 2 compatibility
* remove 2/3 shims in pygments.util
* update setup.py metadata
* Remove unneeded object inheritance.
* Remove unneeded future imports.
|
|\
| |
| | |
Python f-strings: highlight expressions in curly braces
|
| |
| |
| |
| | |
Fixes #1228
|
|/ |
|
|
|
|
|
|
|
| |
- The walrus operator, also known as assignment expressions, was introduced in Python 3.8
- Moves the Token.Operator matching root above Token.Punctuation so the walrus operator takes precedence
- Includes a test to make sure this behavior doesn't regress since it's sensitive to the order of expressions
- Fixes #1381
|
|
|
|
|
|
| |
* Fix glob patterns for directives like Include.
* removing unnecessary escaping.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MIR is a human readable serialization format that's used to represent LLVM's
machine specific intermediate representation. It allows LLVM's developers to
see the state of the compilation process at various points, as well as test
individual pieces of the compiler. Our documentation for the format can be
found at https://llvm.org/docs/MIRLangRef.html.
Adding a lexer for this format will allow the LLVM documentation to contain
syntax highlighted examples of LLVM-MIR. Two lexers are included in this
change. 'llvm-mir' lexes the overall document format and delegates to 'llvm' and
'llvm-mir-body' as appropriate. 'llvm-mir-body' lexes the contents of the 'body:'
attribute and can be used directly to syntax highlight code examples without
including the document boilerplate.
Since the 'llvm-mir' lexer delegates to the 'llvm' lexer at times, this change
also adds the 'immarg' and 'willreturn' keywords to the 'llvm' lexer as these
were missing.
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix lexing of Idris compiler pragmas.
The regex for capturing Idris compiler pragmas did not separate the leading
percent sign from the disjunction of compiler directives correctly, which caused
issues such as "import" or "namespace" keywords to be mishighlighted, due to
confusion with the "%import" and "%name" compiler pragmas.
* Add unit test for Idris compiler directive lexing
|
|
|
|
|
| |
* Add a PEG (Parsing Expression Grammar) lexer
* Add PEG to doc/languages.rst and indicate version
|
|\
| |
| |
| | |
This allows us to resolve the merge conflict properly.
|
| |
| |
| |
| | |
Add Sieve lexer
|
| |
| |
| |
| |
| |
| |
| | |
* haskell: Fix highlighting of promoted type operators
Fixes issue #527
Patch originally written by paamayim
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It supports output from `dmesg`, in that case it highlights based on
keywords in the line
It can also highlight `dmesg -x` output. In that case it uses the
loglevels from the kernel to highlight the lines.
|
| | |
|
| | |
|
| |
| |
| |
| | |
file with incompatible license.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes #1331
All modifications to regex:
1. Delete 2 useless non-capturing groups
2. Variables can not start with underscore (_)
3. Only letters, dot (.) and underscore (_) can go after first dot (.) in name
4. Name from only one symbol dot (.) is possible
|
| |\
| | |
| | | |
Parse HTTP status-line even when reason-phrase not included.
|
| | |
| | |
| | |
| | | |
Background: https://github.com/jakubroztocil/httpie/issues/811
|
| |\ \
| | |/
| |/| |
Add USD lexer
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
string types
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
"Attribute" token
|
| | | |
|
| | | |
|