| Age | Commit message (Collapse) | Author |
|---|
|
|
|
- Resync the lexers with Scintillua
- Update the lexer readme
- Update `zenburn` theme to fix some highlighting issues
- lexers: redirect print function to vis:info()
- Fix support for custom style names
- As per error message "lexer.delimited_range() is deprecated, use lexer.range()".
- Remove remaining `lexer.delimited_range()` call
- Set syntax to `nil` if the file type has no matching lexer
- Updated Go lexer for Go 1.18.
- lexers/dsv: convert to new lexer format
(cherry picked from commit 9edbc3cd9ea1d7142b1305840432a3d2739e755a)
- lexers/gemini: disable legacy gemini lexer
This reverts commit 468f9ee1b027a7ce98b1a249fa1af5888feeb989.
It is in legacy format and of questionable quality. Ideally it
should be contributed upstream from where it will eventually
trickle down to us.
- lexers/git-rebase: convert to new lexer format
(cherry picked from commit 4000a4cc9ac4a4c2869dfae772b977a82aee8d8c)
- lexers/strace: convert to new lexer format
(cherry picked from commit e420451320d97eb164f5629c1bcfab0b595be29d)
- lexers/typescript: add new upstream lexer revision 28e2b60
(cherry picked from commit 7326e6deecdaa75fa94ae9ebdb653f9f907b33f2)
- use `package.searchpath` instead of a local `searchpath` function
- Restore `filetype: support filetype detection via hashbang`
- Remove redundant comment
- Restore gemini lexer
|
|
|
|
|
|
|
|
f4f0f5b allowed "<<-EOF" heredocs to be parsed correctly, but it
introduced a bug that made the lexer fail when the beginning of a
here-doc was the last string in a file (optionally followed only
by blanks).
In order to fix this, move everything regarding "delimiter" within
the block that is executed only if "delimiter" is not nil.
|
|
|
|
|
|
|
|
|
|
If a here-doc start delimiter begins with "-", then spaces are allowed
to come before the closing delimiter.
This patch fixes what would otherwise be parsed incorrectly:
<<-EOF
....
EOF
|
|
|
|
Add a lexer for Mikrotik RouterOS scripts.
https://wiki.mikrotik.com/wiki/Manual:Scripting
|
|
Reorder the list rule such that it matches before the rule for code
blocks. There are still some problems with multiline list items which
are indented and wrongly matched as code blocks.
|
|
This should give the code block rule a chance to actually match
something, whereas before all leading white space was already
consumed.
Fix #823
|
|
|
|
|
|
Upper bound lexing time and cancel highlighting if it is exceeded.
|
|
`operator` variable matches "#", leaving nothing for the comments rule
to match. Since "#" only marks comments in TOML, I just went ahead and
removed the character from the `operator` token.
|
|
According to the TOML github page[1], indentation can be tabs *and/or*
spaces, so `indent_error` is removed.
[1] https://github.com/toml-lang/toml#example
|
|
|
|
|
|
|
|
Adapt in_tag to surrounding coding stlye and use the same simplified
version in html, wsf and xml lexers.
|
|
the new pattern does more or less the same thing, but forward
instead of backward.
|
|
|
|
Fix #665
|
|
Close #761
|
|
TODO: keys should only be highlighted in {} mappings.
|
|
|
|
|
|
Otherwise, show-{tabs,newlines,spaces} replacement characters are
undistinguishable from normal text.
|
|
- Fixed order of rules.
- Some “keywords” were identified as “type”, now corrected.
- Added compiler-specific common __keywords.
- Added boolean and additional integer constants.
- Added support for number suffixes.
- Removed “#if 0“ comments, because it needs some work on the else
branch.
|
|
Or else the following:
<<EOF
....
EOFXYZ
parsers incorrectly.
|
|
http://fantom.org/
|
|
|
|
Adds `extend`, `include`, `module_function` and `require_relative`.
|
|
|
|
Fix #686
|
|
Close #647
|
|
|
|
|
|
See https://reasonml.github.io/docs/en/comparison-to-ocaml.html
for major differences between Reason and OCaml.
|
|
|
|
* fix character literals (#\" no longer quotes the entire file etc.)
* properly nest block comments and support simplified datum comment
* add r7rs keywords, functions and directives
* fix identifiers
- pipes were not recognized as delimiters
- some valid identifiers were not recognized
- some were partially parsed as keywords
- quoting only worked on plain alphanumeric identifiers
* fix numbers (some valid numbers were not recognised)
* dont parse boolean constants as functions
|
|
|
|
This allows to end PHP code sections. Otherwise token is treated as part of the comment and parser continues to parse whatever is after.
|
|
|
|
|
|
|
