]> git.ipfire.org Git - thirdparty/jinja.git/commit
projects / thirdparty / jinja.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 35aa194) | patch
Don't use setlocal in syntax file (#1164)
authorKen Crowell <oeuftete@gmail.com>
Sun, 12 Apr 2020 16:46:08 +0000 (13:46 -0300)
committerGitHub <noreply@github.com>
Sun, 12 Apr 2020 16:46:08 +0000 (09:46 -0700)
commit91eb39b153ce387428d8dc72385440a597cffeca
tree6024d6c0e1d381100dd71f413e54a580d490e49dtree
parent35aa1948c0e80ba864c949ec764edbe9debfc092commit | diff
Don't use setlocal in syntax file (#1164)

I'm not 100% sure that one should not use `setlocal` in a syntax file,
but this breaks other filetypes that may include this syntax file, like
the vim-markdown plugin.  The `comments` and `commentstring` get set for
that markdown buffer with the jinja settings.

See
https://github.com/dhruvasagar/vim-table-mode/issues/162#issuecomment-595317626
for an example of side effects.
ext/Vim/jinja.vim diff | blob | blame | history
Mirror of https://github.com/pallets/jinja.git