-
-
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
Detecting conflicting snippet triggers #1506
Comments
One way to achieve this seems to be the following (seems a bit hackish so, perhaps there is a better way.) Note that it is the snippets with
Then, it is a matter of processing these trigger keywords to see which pairs are subsets of each other. That can be accomplished via the following C++ code:
This shows all the "clashes" for further analysis/correction. |
Hello,
Is there a way to detect incompatible snippet triggers?
Say:
vs
vs
In the above case,
bs
would fire whenbst
is typed, so from the plugin POV there is no conflict, per se.But from the user POV,
bst
will never fire. Is there a way to possibly call a function in UltiSnips that will detect and report such cases?Thanks.
The text was updated successfully, but these errors were encountered: