New answers tagged

1

The error you are getting is happening because your Vim doesn't include support for Python, which is required by UltiSnips, as that plug-in is implemented in Python for the most part. My recommendation is that you should get a Vim binary from your distribution. You mentioned using Linux Mint, so make sure you are not using a vim-tiny package, since that ...


0

This works for markdown files with the vimwiki filetype. The only change needed is the addition ["VimwikiMath", "VimwikiEqIn"] to texMathZones. texMathZones = ['texMathZone' + x for x in ['A', 'AS', 'B', 'BS', 'C', 'CS', 'D', 'DS', 'E', 'ES', 'F', 'FS', 'G', 'GS', 'H', 'HS', 'I', 'IS', 'J', 'JS', 'K', 'KS', 'L', 'LS', 'DS', 'V', 'W', 'X', 'Y', 'Z', 'AmsA', '...


1

You should only set a default value on the first occurrence of the placeholder, that way it works. From :help UltiSnips-mirrors: [...] A mirrored tabstop can have a default value defined. Only the first instance of the tabstop need have a default value. Mirrored tabstop will take on the default value automatically. While the help says "need", it only ...


1

Nevermind, I figured out how to implement it as a custom context snippet: snippet { "braces" "snip.column == len(snip.buffer[snip.line]) - 1" e { $0 } endsnippet


0

I managed to fix my vimwiki ultisnippets by changing the vimwiki file extension to .mdvimwiki and registering it with @ranebrown the UltisnipsAddFiletypes tip. I did not need the let g:vimwiki_table_mappings = 0. This is what I added to my vim.init: autocmd FileType mdvimwiki UltiSnipsAddFiletypes vimwiki " use my custom folder, markdown syntax and ...


2

From this video: UltiSnips evaluates each text object that might have a dependency on some types of text multiple times, to make sure that all dependencies are properly updated. To prevent the date from being updated several times, you could switch to a python interpolation, and use the guard if not snip.c. For example, you could replace this: ** ...


Top 50 recent answers are included