-
-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
g:UltiSnipsEnableSnipMate
won't work if in plugin directory
#1424
Comments
As a workaround of SirVer/ultisnips#1424.
@g6ai UltiSnips reads the variable when it parses a snippet, which happens the first time you expand one. It does not care where the variable is set. Could it be that the problem here is be the order in which Vim executes the Also thanks for providing a docker repo, however I do not know what keys I have to press to reproduce your problem and what you would expect to happen instead of what you see. |
Thank you @SirVer for the info! Here are the order of scripts loaded, for a
Here the variable setting works if I put it in line |
I do not understand what is going on in your case, it seems to me that the loading order is quite bugged. The relevant events as I can see it are these:
The Your data seems to indicate that the Are you using UltiSnips python functions in any files in 16-69? If not, can you try to make your example more minimal and reduce the number of scripts that are executed? |
I have created an absolute minimal config, with only Ultisnips installed. And I tried to reproduce the problem by placing the variable in a So this confirms the problem is not with UltiSnips, but somewhere in my own config. I'll use your advice to try to find the culprit somewhere in line 16-69, thank you very much for your info and time! As this is not an issue of UltiSnips, I should close the issue here :) |
Expected behavior:
g:UltiSnipsEnableSnipMate
to work if it is set in a file in the runtime's plugin directory.Actual behavior:
It only works if it's placed in
init.vim
.The text was updated successfully, but these errors were encountered: