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
Since g:mucomplete#user_mappings is only read once, I was thinking of a buffer variable that is read to extend completions, if these are defined in a ftplugin.
In this example I'm using BufEnter because I think it runs after FileType event, and it wouldn't trigger too often. In the extend function I'm not using error or you'd get an error every time, keep could be used but I think it's not so important.
Addresses #146.
I prefer to use a function rather than a buffer variable because changes
to buffer variables should take effect immediately, which would not be
the case for a hypothetical `b:mucomplete_user_mappings` variable.
Note that existing keys cannot be overridden.
See also: #145.
I don't think that a buffer variable is ideal for the situation you describe. I have added a new function to the current master, which can be used as follows (e.g., in your after/ftplugin/python.vim):
Since
g:mucomplete#user_mappings
is only read once, I was thinking of a buffer variable that is read to extend completions, if these are defined in a ftplugin.In this example I'm using BufEnter because I think it runs after FileType event, and it wouldn't trigger too often. In the
extend
function I'm not usingerror
or you'd get an error every time,keep
could be used but I think it's not so important.The text was updated successfully, but these errors were encountered: