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
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,6 +107,18 @@ If you want to use the omni completion despite the warnings above, execute the f
107
107
108
108
Now when you type Control-X Control-O Vim will hang for a moment, after which you should be presented with an enormous list of completion candidates :-)
109
109
110
+
### The `lua_omni_blacklist` option
111
+
112
+
If you like the omni completion mode but certain modules are giving you trouble (for example crashing Vim) you can exclude such modules from being loaded by the omni completion. You can do so by setting `lua_omni_module_blacklist` to a list of strings containing Vim regular expression patterns. The patterns are combined as follows:
113
+
114
+
" Here's the black list:
115
+
let g:lua_omni_blacklist = ['pl\.strict', 'lgi\..']
116
+
117
+
" Here's the resulting regular expression pattern:
118
+
'^\(pl\.strict\|lgi\..\)$'
119
+
120
+
The example above prevents the module `pl.strict` and all modules with the prefix `lgi.` from being loaded.
121
+
110
122
### The `lua_define_completefunc` option
111
123
112
124
By default the Lua file type plug-in sets the ['completefunc'][] option so that Vim can complete Lua keywords, global variables and library members using Control-X Control-U. If you don't want the 'completefunc' option to be changed by the plug-in, you can set this option to zero (false) in your [vimrc script][vimrc]:
0 commit comments