| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
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.
|
|
|
|
Reported-By: aimixsaka <aimixsaka@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
This is a parallel to https://github.com/martanne/vis/pull/1197
Signed-off-by: Matěj Cepl <mcepl@cepl.eu>
|
|
This closes https://github.com/martanne/vis/issues/1196.
|
|
This'll patch vis.lexers.load to return nil when the lexer could not be
found. Previously it would've errored out, which the load in lexer.lua
still will as this is used in lexers themselves.
Another possibility is to only patch set_syntax in vis.lua and the
WIN_HIGHLIGHT handler in vis-std.lua, but as most references to
vis.lexers.load already handle a nil return, this seems better.
|
|
fixes #1190: Missing mail.lua lexer
|
|
used by the following lexers: gemini, markdown and txt2tags to
highlight sections of code.
|
|
This allows for example to complete file names in markdown images.
E.g.:  (hint: variables in lua already handle this).
|
|
This will break all plugins which currently use Win.viewport.
|
|
|
|
This also involves modifying the style definitions so that they
include sub tags as well. For example command.section in latex
should be mapped to COMMAND_SECTION.
|
|
Caching lexers causes lexer tables to be constructed once and
reused during each HIGHLIGHT event. Additionally it allows to
modify the lexer used for syntax highlighting from Lua code.
This is used for example for the syntax aware spellchecking
performed by the vis-spellcheck plugin.
|
|
vis{,-std}.lua:
* replace removed _TOKENSTYLES with _TAGS
* don't add default styles to the lexer. lexers no longer
define their own styles
filetype.lua: update path detection for scintillua 6.2
|
|
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.
|
|
The old style handling had a lot edge cases where one of the
colours or the attribute wouldn't get applied correctly. This
commit adds a new style_set() method to the Ui which should be
called instead of manually touching a cell's style. This also
means that the Cell struct can be made opaque since all the
handling is now done inside the ui-terminal files.
With this it is now viable to combine the light and dark 16 colour
themes into a single base-16 theme. This theme works very well
with the Linux virtual console and will now be the default theme
regardless of if the terminal supports 256 colours or not. This
should address the common complaints about vis not respecting the
users default terminal colours.
fixes #1151: Theming is sometimes partially applied or ignored
see #1103: terminal no longer has transparency/opacity
see #1040: Transparent background and setting options by default
|
|
|
|
|
|
|
|
|
|
Internally vis supports unicode just fine. Instead of relying on
external programs utilize vis' own features.
Thanks to Florian Fischer for the correct regex!
|
|
There is the textadapt module for dealing with Modula 2
by the late Nikalus Wirth and its successor Modula 3 on
https://github.com/paaguti/textadept-modula-lexers. If I want to
just use it, I need to have these types recognized.
|
|
|
|
This allows to complete file names in latex code (e.g. `\include{foo}`).
|
|
This hasn't worked in almost a year and even if it did it makes no
sense. Based on my testing lexing takes a couple milliseconds at
most. If it took 1 second (the default value for this option) vis
would be completely unusable.
If people want support for this it should be submitted upstream
and vis will act based on the outcome of that.
closes #1122: lexer no longer obeys redrawtime
|
|
This obviously draws on the alt_name parameter used in scintillua
but rather then passing it all the way up to the chain to
lexers.load() we will just handle it in set_filetype().
8a420ec accidently readded detection for the removed git-commit
lexer which somehow went unnoticed until we readded caching for
the new lexers. Instead of just removing it we can alias to the
diff filetype and only set the colorcolumn for commit messages.
This fixes the incorrect behaviour of adding a colorcolumn to diff
and patch files and thus completely reverts 0cc684f.
|
|
As defined in https://peps.python.org/pep-0484/#stub-files.
|
|
There are probably more things to simplify but at least this makes
it easier to see what exactly is different between `<C-x><C-f>` and
`<C-x><C-o>`.
Some differences were removed:
* whitespace in range is treated the same for both actions
* empty range will expand to files in CWD for both actions
closes #1146: Complete file name and file path swapped in doc
|
|
same as last commit, `fstab.lua` shouldn't be matched as `fstab`
|
|
The current literal file name detection for GNUmakefile, makefile
or Makefile could match anywhere in the file name.
For example the file type of `makefile.lua` (the name of our makefile lexer)
was detected as makefile.
This is fixed by requiring the literal patterns to start and end with
the string.
|
