vim/UltiSnips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use <nomodeline> when firing user autocmds

Browse Source 
As recommended by the Vim help (`:h <nomodeline>`):

    After applying the autocommands the modelines are
    processed, so that their settings overrule the
    settings from autocommands, like what happens when
    editing a file. This is skipped when the <nomodeline>
    argument is present. You probably want to use
    <nomodeline> for events that are not used when loading
    a buffer, such as |User|.

Fixes: https://github.com/SirVer/ultisnips/issues/542
This commit is contained in:
Greg Hurrell 2015-08-06 22:47:29 -07:00
parent b3cd0cae14
commit 3eabbe71a3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pythonx/UltiSnips/snippet_manager.py
View File

@ -374,7 +374,7 @@ class SnippetManager(object):
'autocmd CmdwinLeave * call UltiSnips#LeavingBuffer()')
_vim.command('augroup END')
_vim.command('silent doautocmd User UltiSnipsEnterFirstSnippet')
_vim.command('silent doautocmd <nomodeline> User UltiSnipsEnterFirstSnippet')
self._inner_state_up = True
def _teardown_inner_state(self):
@ -382,7 +382,7 @@ class SnippetManager(object):
if not self._inner_state_up:
return
try:
_vim.command('silent doautocmd User UltiSnipsExitLastSnippet')
_vim.command('silent doautocmd <nomodeline> User UltiSnipsExitLastSnippet')
if self.expand_trigger != self.forward_trigger:
_vim.command('iunmap <buffer> %s' % self.forward_trigger)
_vim.command('sunmap <buffer> %s' % self.forward_trigger)