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

Cf. #591: Added doc on UltiSnips autotrigger

Browse Source
This commit is contained in:
Karl Yngve Lervåg 2016-10-10 21:56:38 +02:00
parent abf50a3f04
commit a9b99ef1c8
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/vimtex.txt
View File

@ -1371,6 +1371,8 @@ Explanation of the keys:
function, please see the source for examples on how the |vimtex| wrappers
are written.
*vimtex-neosnippet*
*vimtex-UltiSnips*
Note: that this feature is not the same as the snippet feature of |UltiSnips|
or |neosnippet|. The imaps feature of |vimtex| previously supported `automatic`
snippets, but these have been removed after careful considerations and input
@ -1390,6 +1392,12 @@ show how to create such mappings: >
inoremap <silent> __ __<c-r>=UltiSnips#Anon('_{$1}$0', '__', '', 'i')<cr>
inoremap <silent> ^^ ^^<c-r>=UltiSnips#Anon('^{$1}$0', '^^', '', 'i')<cr>
A drawback with the anonymous UltiSnips snippets is that they do not nest.
That is, if you did `__` twice in a row, only the second one could be escaped.
In recent versions of |UltiSnips|, one may set normal snippets to trigger
automatically, see |UltiSnips-autotrigger|. This allows nesting, and is
therefore a better approach than using the anonymous snippet function.
------------------------------------------------------------------------------
Events~
*vimtex-events*