0
0
mirror of https://github.com/vim/vim.git synced 2025-07-26 11:04:33 -04:00
Lifepillar 0bca4a0018
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>
2023-12-27 18:49:50 +01:00
..
2008-06-24 22:58:06 +00:00
2022-12-11 15:53:04 +00:00
2021-09-09 21:55:11 +02:00
2021-09-09 21:55:11 +02:00
2022-07-25 15:42:07 +01:00
2022-03-30 10:51:39 +01:00
2016-10-23 21:21:08 +02:00
2021-09-21 20:09:51 +02:00
2021-09-09 21:55:11 +02:00
2022-07-01 18:45:04 +01:00
2021-09-09 21:55:11 +02:00
2010-01-06 20:54:52 +01:00
2021-09-09 21:55:11 +02:00
2021-09-09 21:55:11 +02:00
2019-11-10 22:09:11 +01:00
2020-09-19 18:50:13 +02:00
2023-05-14 18:50:25 +01:00
2022-03-30 10:51:39 +01:00
2023-02-27 15:49:53 +00:00
2021-09-09 21:55:11 +02:00
2006-04-15 20:16:09 +00:00
2019-01-01 15:32:17 +01:00
2021-06-27 15:18:56 +02:00
2023-10-16 09:53:37 +02:00
2021-09-09 21:55:11 +02:00
2021-05-02 17:19:11 +02:00
2023-10-16 09:53:37 +02:00
2016-09-25 22:11:48 +02:00
2021-09-09 21:55:11 +02:00
2020-03-01 19:06:45 +01:00

The autoload directory is for standard Vim autoload scripts.

These are functions used by plugins and for general use.  They will be loaded
automatically when the function is invoked.  See ":help autoload".

gzip.vim	for editing compressed files
netrw*.vim	browsing (remote) directories and editing remote files
tar.vim		browsing tar files
zip.vim		browsing zip files
paste.vim	common code for mswin.vim, menu.vim and macmap.vim
spellfile.vim	downloading of a missing spell file

Omni completion files:
ccomplete.vim		C
csscomplete.vim		HTML / CSS
htmlcomplete.vim	HTML
javascriptcomplete.vim  Javascript
phpcomplete.vim		PHP
pythoncomplete.vim	Python
rubycomplete.vim	Ruby
syntaxcomplete.vim	from syntax highlighting
xmlcomplete.vim		XML (uses files in the xml directory)