| 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
|
|
|
|
|
|
This uses gsub instead of find+sub. Also changes an ignoresuffix
pattern from /~$/ to /~+$/ which should reduce iterations.
|
|
https://harelang.org
|
|
|
|
|
|
|
|
add 2 tables, hashbang and utility for vis.ftdetect.filetypes.<lang>
fetch utility from /usr/bin/env args (mostly)
Support -S for /usr/bin/env args, discard variables=value args
|
|
This filename is set when writing a commit message in git.
If you run git-commit with an --verbose option or if you just have set
it in your git-config, that shows you the patch diff on bottom
of the file.
Unfortunately, now every patch file will set colorcolumn, but overall
I think this is better than having duplicated lexers.
|
|
Some AUR helpers use this (e.g. paru).
|
|
|
|
|
|
|
|
|
|
|
|
This is useful when writing "debian/rules" files in packages.
|
|
|
|
|
|
|
|
These are either accidentally global or unused variables. In the file
type pluging the mime type variable was wrongly scoped, meaning the
text/plain settings applied to all otherwise unknown files.
|
|
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
|
|
|
|
|
|
There is no .lily file but there is a .ily file in lilypond for
stylesheets. They are like css for lilypond. See here:
http://lilypond.org/doc/v2.18/Documentation/learning/style-sheets
|
|
Node.js uses .mjs and .cjs extensions, both are regular javascript.
|
|
|
|
|
|
|
|
|
|
|
|
Add a lexer for Mikrotik RouterOS scripts.
https://wiki.mikrotik.com/wiki/Manual:Scripting
|
|
This covers other detection, so make sure to match it in
last resort only.
|
|
Close #868
|
|
|
|
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.
|
