diff options
author | Lifepillar <lifepillar@users.noreply.github.com> | 2023-12-27 18:49:50 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-12-27 18:49:50 +0100 |
commit | 0bca4a00188ccde335e0d6a7b7c093998e09182f (patch) | |
tree | 0daabf9cf36a8e05f51f39f9e5a734d80f5414a8 /runtime/doc/ft_context.txt | |
parent | cea3dac76e42c9a33dccbd2f10ef011f0be5c292 (diff) |
runtime(context): update ConTeXt keywords and other minor fixes (#13778)
Update to the ConTeXt runtime files. Changes:
1. shared syntax files updated with `mtxrun --script interface --vim`
using the latest ConTeXt LMTX.
2. fixed reference to `make` tag in the help file.
3. added `keepend` to mitigate issues with embedded Lua syntax (see
below).
4. the latest revision date of each ConTeXt runtime file has been
updated to the date of this commit.
The issue about embedded Lua was reported by a user:
>Take the following valid ConTeXt file:
> \starttext
> \ctxlua{context("Text generated from Lua.")}
> \ctxlua{context("Another text generated from Lua.")}
> \stoptext
>On my Vim installation (including when I start Vim with `--clean`), the
>closing bracket and curly braces on line 2 are highlighted red and the
>syntax highlighting after that is off.
>I was trying to dig a little bit into what was going on, using the
>`synID()` and `synIDattr()` functions. It appears that the closing
>bracket on line 2 is matched as a `luaParentError` instead of the end
>of the `luaParen` region. Therefore, the `luaParen` region continues
>all the way to the end of the file. The closing curly brace on line
>2 is matched as a `luaError`, the 2nd `\ctxlua` on line 3 as
>`luaParen`, etc.
>This issue doesn't occur in a plain Lua file, where the closing bracket
>is correctly matched as the end of the `luaParen` region. So it seems
>that something goes wrong when the Lua syntax file is included in the
>ConTeXt one.
By adding `keepend`, the right parenthesis for some reason is still
highlighted as a `luaParenError`, but at least the right curly brace
should correctly end the Lua block.
From what I've seen, I think it is very difficult to embed Lua syntax
properly without help from the Lua syntax file (that is, without
patching it). It has global rules such as:
syn match luaParenError ")"
syn match luaError "}"
which make it difficult, if not impossible, to contain Lua syntax
without `keepend` (and its limitations).
Signed-off-by: Lifepillar <lifepillar@lifepillar.me>
Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime/doc/ft_context.txt')
-rw-r--r-- | runtime/doc/ft_context.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/runtime/doc/ft_context.txt b/runtime/doc/ft_context.txt index 6303357ec7..43872529c5 100644 --- a/runtime/doc/ft_context.txt +++ b/runtime/doc/ft_context.txt @@ -1,4 +1,4 @@ -*ft_context.txt* For Vim version 9.0. Last change: 2022 Sep 27 +*ft_context.txt* For Vim version 9.0. Last change: 2023 Dec 26 This is the documentation for the ConTeXt filetype plugin. @@ -103,13 +103,13 @@ Stop all the ConTeXt jobs currently running in the background. Settings ~ *'b:context_ignore_makefile'* *'g:context_ignore_makefile'* -`:make` can be used to (synchronously) typeset a document. If a Makefile exists +|make| can be used to (synchronously) typeset a document. If a Makefile exists and this option is not set, standard `make` is used. If this option is set, `mtxrun` is invoked instead, even if a Makefile exists. > g:context_ignore_makefile = 0 < -NOTE: before using `:make`, set the working directory of the buffer to the +NOTE: before using |make|, set the working directory of the buffer to the directory of the file to be typeset. *'g:context_extra_options'* |