| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/ / / |
|
| | | | |
|
| | | | |
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* lexers: add Elpi
* test: elpi
* Fix copyright
* address code review
|
| | |
| | |
| | |
| | |
| | | |
This includes a new structural diff which is more robust, as it handles
changes like different attribute order.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
chillibits-master
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
blu-base-lexers_ef
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* New lexer for Sophia contracts
* Whitespacee should be Text.Whitespace
* Update golden files
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Create BDD.py
Initialize the lexer file of BDD
Add keywords of BDD
* Update the 'RegexLexer'
* Edit and test
* Update BDD.py
* Update BDD.py
* Update the BddLexer file
* Update the BddLexer of root tokens
* edit bdd
Add regular expression for tokens
* edit bdd
Add regular expression for tokens
* add .gitignore
* updata bdd.lexer
* Delete bdd.py
* Update the Keywords, Numbers, Punctuation token
* bdd.py
Assign different colors to keywords, punctuation, numbers, and variables.
* Update the BddLexer file
* Update bdd.py
Fix the file name.
* Add the detection for '@'
Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com>
* Update bdd.py
Add detection of double quotes.
Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com>
* Fix the double quotes
* fix the quote recognition
* add comments
* update the root dir
* add bdd test cases
* Delete .DS_Store
* Delete .DS_Store
* Delete .DS_Store
* remove DS file
* restore the gitignore file
* update the bdd lexer
* update the bdd lexer
* update the whitespace highlight
* update the whitespace highlight
* refactor the bdd.py
* update the punctuation
* update the punctuation
* update bdd token
Change "." to the "\S+",
Which reduce the test output file size.
Co-Authored-By: OMGJL <8707895+OMGJL@users.noreply.github.com>
* Update bdd.py
Reduce the new token for each space
Co-authored-by: Hongyuan Yan <hongyuan.yan@student.adelaide.edu.au>
Co-authored-by: OMGJL <lzhsjunkmail@gmail.com>
Co-authored-by: Hongyuan Yan <54675432+kirito330824@users.noreply.github.com>
Co-authored-by: Jessie2110 <71688609+Jessie2110@users.noreply.github.com>
Co-authored-by: Jessie2110 <wuqiong2110@gmail.com>
Co-authored-by: OMGJL <8707895+OMGJL@users.noreply.github.com>
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* 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
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* add a lexer for .SRCINFO files
* add an example file that tests architecture dependent keys
* fix module name underline
|
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Add lexer for the Savi language.
* Updates based on review comments.
* Prefer Text.Whitespace token over Text token for whitespace.
* Updates to Savi lexer based on changes to Rouge Savi lexer.
* Add versionadded identifier to Savi lexer.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add a lexer for the sed scripting language
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Sed is a stream editing scripting language forming part of the POSIX
standard. This means that sed cn be found as part of any POSIX compliant
OS such as Linux, MacOS, and the BSDs. This lexer supports the complete
POSIX standard for sed as well as various GNU extensions.
The names 'gsed' and 'ssed' may sometimes be used as part of a file
extension to refer specifically to GNU sed or Super Sed, two popular
implementations of sed.
The sed language is rather simple, here is a quick overview:
- Comments begin with a '#' and continue to the end of the line.
- Commands can be prepended with a range that selects lines. This can be
either a number ([0-9]+), a '$', or a regular expression. Regular
expressions can either be enclosed in '/' such as /regex/ or they can
be exclosed in any other character however the opening delimiter must
be escaped, for example: \@regex@.
- Some commands such as 'w', 'r', and 'b' take a string as a parameter,
this string extends either to the next ';' or newline.
- Some commands such as 'a' can take multiline strings.
- Commands can be grouped with braces ('{' and '}').
- The 'y' command takes two strings as parameters, seperated by any
delimiter ('y/abc/123/' or 'y|abc|123|')
- The 's' command is like the 'y' command but the fist parameter is a
regular expression. Additionally it takes an optional 3rd parameter
which are a sequence of flags ('s|regex|replace|flags').
I chose to add support for GNU sed extensions as it is by far the most
used implementation.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
blu-base-lexers_de
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
fixes #1949
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Part of #1718.
|
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Some dark styles did not define a color for every token type,
resulting in black text (the browser default for text) on dark
backgrounds (defined by the styles) unless the web page had some
CSS to remedy that like:
body { color: white; background: black; }
We however don't want the readability of styles to rely on external CSS.
Part of #1718. Fixes some unreadable styles reported in #1526.
|
| | | | |
| | | | |
| | | | | |
Part of #1718.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Use a simpler expression to match comments in HTML/XML.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Correctly identify whitespace.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Correctly identify whitespace.
* Merge consecutive tokens where possible.
* Consistently use String.Double for the opening and closing quotation
marks
|