aboutsummaryrefslogtreecommitdiff
path: root/runtime/example_init.lua
diff options
context:
space:
mode:
authorzeertzjq <zeertzjq@outlook.com>2026-05-17 16:49:24 +0800
committerzeertzjq <zeertzjq@outlook.com>2026-05-17 16:49:27 +0800
commit1b6063db591b27bfb01ba2b928c8e2ff0833e2db (patch)
tree9e4dea887a31183927d8705c24c17ef0d5275a26 /runtime/example_init.lua
parent7d99104058fd2653903830c2b39b42d80092e646 (diff)
downloadrneovim-1b6063db591b27bfb01ba2b928c8e2ff0833e2db.tar.gz
rneovim-1b6063db591b27bfb01ba2b928c8e2ff0833e2db.tar.bz2
rneovim-1b6063db591b27bfb01ba2b928c8e2ff0833e2db.zip
vim-patch:8b25d90: runtime(django): Resolve FIXME of comparrison operators + localization tags
Summary: Add highlight of comparison operators resolving FIXME left by maintainer. How it works: By creating a the variable ‘djangoOperator’ with the regex and defining to only highlight when enclosed within ‘djangoTag’ and ‘djangoVarBlock’ the highlight works as expected. Note: Note even though the maintainer had left the note “FIXME ==, !=, <, >, <=, and >= should be djangoStatements” the results do work as I think he intended even though the variable ‘djangoOperator’ had to be created to achieve the result. By doing it this way the highlight process does not get confused depending on the spacing of the comparison operator. Example: {{ x>=10 }} and {{ x >= 10 }} work as expected. Add tags related to localization. Documentation source: - https://docs.djangoproject.com/en/5.2/topics/i18n/formatting/#controlling-localization-in-templates closes: vim/vim#20225 https://github.com/vim/vim/commit/8b25d90b087fdc5cd2bc120a4aff414d080de53c Co-authored-by: tecis <67809811+tecis@users.noreply.github.com>
Diffstat (limited to 'runtime/example_init.lua')
0 files changed, 0 insertions, 0 deletions