You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
user_trigger_map correspondents to the g:ycm_semantic_triggers here, and gets merged with PREPARED_DEFAULT_FILETYPE_TRIGGERS.
Therefore it's not possible anymore to unset/change the filetype triggers for a specific filetype.
Also, this recent change (merging the settings) appears to be not backwards-compatible in that g:ycm_semantic_triggers was taken as-is before, without merging it with the defaults.
The text was updated successfully, but these errors were encountered:
Therefore it's not possible anymore to unset/change the filetype triggers for a specific filetype.
This was changed many months ago and is working as intended. Yes, you can't turn off default semantic triggers anymore; people were turning them off by accident when they would redefine the dict to add triggers for a random language. Removing some default semantic triggers for a language was thus a rarely used feature that was removed because it did more harm than good (people were shooting themselves in the foot).
The whole idea of user-level custom semantic triggers was a bad one and I'd take it back if I could without breaking people. It results in people locally setting semantic triggers for a language YCM doesn't have good defaults instead of upstreaming their changes and improving the defaults. This is the reason why there's no user-level option for tweaking the new per-language identifier regex.
Code: https://github.com/Valloric/ycmd/blob/master/ycmd/completers/completer_utils.py#L26-L31
user_trigger_map
correspondents to theg:ycm_semantic_triggers
here, and gets merged withPREPARED_DEFAULT_FILETYPE_TRIGGERS
.Therefore it's not possible anymore to unset/change the filetype triggers for a specific filetype.
Also, this recent change (merging the settings) appears to be not backwards-compatible in that
g:ycm_semantic_triggers
was taken as-is before, without merging it with the defaults.The text was updated successfully, but these errors were encountered: