Using: gvim8.1 32-bit (downloaded from vim.org) on Windows 10; latest clang_complete in dll mode (embedded), with Windows 32-bit python 3.6 and official Windows llvm/clang download (32-bit) as follows:
clang version 7.0.1 (tags/RELEASE_701/final)
Target: i686-pc-windows-msvc
The setup works fine, auto-complete works, but occasionally it locks some files up, so cannot save them. The only way to unlock when it gets into this is close gvim and open it again, which is very counter-productive.
It appears that clang or the python wrapper of it, is called in a mode that ends up locking the files?
Would appreciate suggestions to work around this one; or a code fix!
Using: gvim8.1 32-bit (downloaded from vim.org) on Windows 10; latest clang_complete in dll mode (embedded), with Windows 32-bit python 3.6 and official Windows llvm/clang download (32-bit) as follows: clang version 7.0.1 (tags/RELEASE_701/final) Target: i686-pc-windows-msvc
The setup works fine, auto-complete works, but occasionally it locks some files up, so cannot save them. The only way to unlock when it gets into this is close gvim and open it again, which is very counter-productive.
It appears that clang or the python wrapper of it, is called in a mode that ends up locking the files?
Would appreciate suggestions to work around this one; or a code fix!
Thanks