Error Detected While Processing Function Clang_complete
Sign in Pricing Blog Support Search GitHub This repository Watch 85 Star 1,301 Fork 251 Rip-Rip/clang_complete Code Issues 131 Pull requests 16 Projects 0 Wiki Pulse Graphs clang_complete vim New issue Undefined variable l:res #158 Closed ivan-cukic opened this Issue Jun 19,
Clang_complete Plugin
2012 · 14 comments Projects None yet Labels None yet Milestone No milestone Assignees No one
Error Detected While Processing Function Youcompleteme#enable
assigned 5 participants ivan-cukic commented Jun 19, 2012 When using libclang 3.1, the following error message appears: "Undefined variable l:res" in 520 function! ClangComplete(findstart, base) The issue is raised because the
Error Detected While Processing Function Ultisnips#cursormoved
line doesn't work for some reason (will investigate further why): 556 python vim.command('let l:res = ' + str(getCurrentCompletions(vim.eval('a:base')))) This removes the error, but completion doesn't work: 554 if g:clang_use_library == 1 +555 let l:res = [] 556 python vim.command('let l:res = ' + str(getCurrentCompletions(vim.eval('a:base')))) 557 else 558 let l:res = s:ClangCompleteBinary(a:base) 559 endif Owner Rip-Rip commented Jun 21, 2012 Did you try with error detected while processing function loadrope the latest vim version? Because it works for me with libclang 3.1 and vim 7.3.547 ivan-cukic commented Jun 21, 2012 Yes, vim 7.3.547 here as well. Might be a problem in 64bit version? Unfortunately, I haven't had the time to dive deeper into the issue. Hoping I'll be able to do it soon :/ lineinthesand commented Jun 29, 2012 I use the latest clang_complete from git (cloned yesterday). I compiled the latest llvm/clang (svn, co yesterday) from source, and let g:clang_library_path="/usr/local/lib64", then I let g:clang_use_library=1. After trying completion of a struct member, I get these errors: Error detected while processing function ClangComplete: line 35: Traceback (most recent call last): Press ENTER or type command to continue Error detected while processing function ClangComplete: line 35: File "", line 1, in Press ENTER or type command to continue Error detected while processing function ClangComplete: line 35: NameError: name 'vim' is not defined Press ENTER or type command to continue Error detected while processing function ClangComplete: line 40: E121: Undefined variable: l:res Press ENTER or type command to continue Error detected while processing function ClangComplete: line 40: E15: Invalid expressio
Sign in Pricing Blog Support Search GitHub This error detected while processing function nerdtree#ui_glue#invokekeymap repository Watch 508 Star 11,987 Fork 1,400 Valloric/YouCompleteMe Code error detected while processing function vundle#installer#new Issues 55 Pull requests 7 Projects 0 Wiki Pulse Graphs New issue Error error detected while processing function gzip#read on start: Error detected while processing function youcompleteme#Enable..80_SetUpPython #1652 Closed dvinothkumar opened this Issue Aug 26, 2015 · 23 comments Projects None https://github.com/Rip-Rip/clang_complete/issues/158 yet Labels None yet Milestone No milestone Assignees No one assigned 12 participants dvinothkumar commented Aug 26, 2015 I get this error, when starting gvim. This looks very similar to the issue #1281 at #1281. People in that thread reported that doing https://github.com/Valloric/YouCompleteMe/issues/1652 "git submodule update --init --recursive" fixed the issue. But not for me. I'd appreciate if someone can help me with this. Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: Traceback (most recent call last): Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: File "", line 25, in Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: File "/root/.vim/bundle/YouCompleteMe/autoload/../third_party/ycmd/ycmd/utils.py", line 277, in SafePopen Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: return subprocess.Popen( args, *kwargs ) Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: File "/usr/local/lib/python2.7/subprocess.py", line 710, in init Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: errread, errwrite) Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: File "/usr/local/lib/python2.7/subprocess.py", line 1335, in _execute_child Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: raise child_exception Error detected while processing function youcompleteme#Enable..80_SetUpPython: line 34: OSEr
using Pathogen (i. e., I installed it as https://www.nesono.com/node/437 a submodule of my dotfiles git repository aka nesono-bin. I tried to be smart and went into the submodule's directory and invoked make install. That nicely built the vimball and installed itself - but whenever error detected I tried to open a cpp-file I got the followingerror: "/tmp/sample.cpp" 10L, 144C Error detected while processing function 15_ClangCompleteInit..15_initClangCompletePython: line 29: Traceback (most recent call last): File "", line 1, in File "/Users/iss/nesono-bin/vim/bundle/clang_complete/plugin/libclang.py", line 63, error detected while in initClangComplete Config.set_compatibility_check(False) File "/Users/iss/nesono-bin/vim/plugin/clang/cindex.py", line 3126, in set_compatibility_check raise Exception("compatibility_check must be set before before " \ Exception: compatibility_check must be set before before using any other functionalities in libclang. line 30: E121: Undefined variable: l:res E15: Invalid expression: l:res == 0 The error message was caused by the fact, that vim was loading clang_complete twice, as it was now installed in the bundle directory and in the plugin directory. To fix this issue, I deleted all clang_complete relatedfiles: bin/ doc/clang_complete.txt doc/tags plugin/clang/ plugin/clang_complete.vim plugin/libclang.py plugin/snippets/ Everything worked pretty fine from now on. That's it again iss nesonoView the discussion thread. iss's blog