We accidently parsed the whole python bindings whenever we changed the file that is in the vim buffer. This does not only cost runtime, but it also yields to locking problems as we may allocate more than one lock. Signed-off-by: Tobias Grosser <email@example.com>
This fixes an error that arise because vim variables are not yet available in the thread's context. This was the original error message: Error detected while processing function <SNR>50_Detect: E121: Undefined variable: b:clang_user_options E15: Invalid expression: b:clang_user_options Exception in thread Thread-1: Traceback (most recent call last): File "C:\Python27\Lib\threading.py", line 530, in __bootstrap_inner self.run() File "SOMEPATHHERE/plugin/libclang.py", line 223, in run getCurrentTranslationUnit() File "SOMEPATHHERE/plugin/libclang.py", line 23, in getCurrentTranslationUnit userOptionsLocal = splitOptions(vim.eval("b:clang_user_options")) vim.error: invalid expression Signed-off-by: Tobias Grosser <firstname.lastname@example.org>
Ignore `tags' files created when using pathogen.
…e 'args_pos' when filling the dictionnary used by vim for the completion.
I didn't tested it with ultisnips but due to the similarity of the code, it should works. Some features were removed for now and may be reintroduced in the future.
Moved LICENSE and TODO files into doc/clang_complete.txt. This will ensure these texts are included when the plugin is distributed as the .vba file. Moved cc_args.py to bin/cc_args.py. So it doesn't clutter the user's ~/.vim Updated cc_args.py section of the docs to refer to its installed location