| Age | Commit message (Collapse) | Author | Files | Lines |
|
... and replace the functions for unsigned integers with their
signed equivalents, using a type cast where needed.
Actually the functions for unsigned integers were deprecated since
lua 5.3...
https://www.lua.org/manual/5.3/manual.html#8.3
Also lua_newstate() requires a third argument since 5.5...
https://www.lua.org/manual/5.5/manual.html#8.3
Finally the key in a for loop is now const, so use a temporary
variable instead.
|
|
Bugfixes:
- Fixed Pascal numeric literals.
- Fixed folding of HTML/XML comments and XML processing
instructions.
- Fixed incorrectly highlighting '..' range operators between
numbers.
Changes:
- Added Janet and todo.txt lexers.
- Updated Python lexer to recognize t-strings.
- Migrated ini and Dart lexers.
- Updated org lexer word lists.
|
|
This is an amalgamation of the following upstream commits:
- Overhauled API documentation for lexer.lua.
- Fixed Markdown to allow code fence blocks to be indented.
- Use GitHub Pages' Primer theme for documentation.
Build static pages with Jekyll, like GitHub Pages does.
- Migrated systemd lexer.
Thanks to Matěj Cepl.
- Migrated Lisp lexer and highlight character escapes.
Thanks to Matěj Cepl.
- Migrated rpmspec lexer and made some improvements.
Thanks to Matěj Cepl.
- Modernized reST lexer.
Thanks to Matěj Cepl.
- Markdown lexer should just tag the start of a blockquote.
The quote's contents may contain markdown.
- Output lexer can highlight CSI color sequences.
- Allow lexers to define their own fold functions.
- Added custom folder for Markdown headers.
- Added `lexer.line_start`, `lexer.line_end` and `lexer.text_range()`.
- Fixed Markdown lexer to not lex some continuation lines as code.
- Fixed SciTE not using Scintillua's markdown lexer.
- Markdown lexer should not highlight secondary paragraphs in list items as code blocks.
- Have SciTE recognize CMakeLists.txt.
|
|
|
|
Thanks to Samuel Marquis.
|
|
|
|
Thanks to Samuel Marquis.
|
|
Thanks to John Benediktsson.
|
|
Originally this was to prevent clashes with Textadept's language-specific key handling, but this is
no longer applicable.
|
|
|
|
The lexer runs without error, but still does not really work.
|
|
|
|
|
|
|
|
|
|
|
|
It is not clear how large this value should be. It appears to be a function of grammar complexity.
For example, a problematic HTML file requires a value of 1329 to work, but removing either the
'attribute' rule or an embedded lexer reduces the limit.
However, identifying which files trigger a stack overflow is not trivial. It does not appear to
depend on file size. For example, the problematic HTML file is 125K, but a non-problematic HTML
file of 500K works.
|
|
Based on contribution from Samuel Marquis.
|
|
Instead of highlighting non-whitespace characters one at a time,
highlight whole ranges.
|
|
Relates-to: https://github.com/orbitalquark/scintillua/issues/68
Relates-to: https://github.com/orbitalquark/scintillua/commit/dee7d765a005
Signed-off-by: Matěj Cepl <mcepl@cepl.eu>
|
|
This combines:
Added 'done' literal to Hare lexer.
Initialize fold constants when Scintillua is used as a standalone library.
|
|
Based on the advice from the upstream maintainer of Scintillua
(gh#orbitalquark/scintillua#87).
|
|
Rather than cherry pick patches from after 6.2 we will just grab
everything as is.
|
|
|
|
- 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
|