Error detected while processing function vim

Why do I suddenly receive «Error detected while processing function 30_Highlight_Matching_Pair»?

I suddenly receive Error detected while processing function 30_Highlight_Matching_Pair when I want to write parantheses or when moving over parantheses. I can turn off these error message with

Unfortunatly, I am unable to reconstruct what I have changed in my environment, possibly in the vimrc file. Does someone have an idea where I have to look to turn this behavior off?

1 Answer 1

The error you see, comes from the plugin matchparen, that is distributed with vim and which does highlight the matching parenthesis as you edit them. Internally is uses the searchpairpos() function.

Starting with Vim patch 8.1.0112, Vim will throw an error, if the skip argument for the functions searchpair() and searchpairpos() is not a string argument.

That caused the error message invalid argument: 0 , because the two plugins matchparen and matchpair that come with Vim, used a skip expression of 0 .

So a bit later, those two plugins have been changed to make use of a skip expression of ‘0’ . So patch 8.1.115 fixed the matchparen plugin and patch 8.1.143 fixed a related problem with the matchit and matchparen plugin, that should keep Vim responsive, even when the pattern is not found.

If you still see the error, even after you have installed a Vim version later than 8.1.143, that means you most likely have an older matchparen plugin laying around and are not using the latest version that comes with Vim. So make so to update the runtime files properly and delete older plugins in case you have them in your local .vim path as well.

Источник

Error detected while processing function snipMate#TriggerSnippet #264

Minimal working example, of a JavaScript file:

Upon pressing the tab key in insert mode, with the cursor right after the curly bracket, the following error is shown:
Error detected while processing function snipMate#TriggerSnippet[35]..snipMate#GetSnippetsForWordBelowCursor[31]..funcref#Call[61]..snipMate#GetSnippets[4]..funcref#Call[61]..snipMate#DefaultPool[13].. 117_Glob: line 5: E220: Missing >.

Other than SnipMate, I’ve installed the required dependency plugins: vim-addon-mw-utils and tlib. I’ve also installed vim-snippets.

I’m running the console version of Vim 8 (32bit) on Windows 10.

The text was updated successfully, but these errors were encountered:

Sorry for the late response. I can confirm this bug is present, and it looks like there are other issues with SnipMate on Windows as well. I’ll have to look into this.

I’ve determined this to be a bug in Vim in how glob() functions on Windows. I haven’t yet determined a proper solution, either to the bug or a workaround in SnipMate. Getting rid of support for single snippet files would work, but I’m not sure I’m ready to do that.

I do confirm that this issue is not resolved yet

@ajzafar This appears to not be unique to Windows as I have this exact issue on macos (Catalina, 10.15.7) as well, both in neovim nightly and vim8.

I have the same error in Linux Mint Cinnamon 20.1.

I started getting this with an existing vim session Ubuntu 21.04 at a random moment. Then I nuked

/.vim/session and next time it started working again. So it’s some intermediate state. A minimal repro would be needed.

/.vim/session what is it? and is there anything that can serve as an alternative ?

Sorry, I don’t know the exact cause, this was a sledgehammer random fix attempt that worked.

I suggest you try to bisect your configs and tell us the result 🙂

It seems like there might be a few related bugs going on here. I want to try something to fix them all. I just pushed a branch that disables support for .snippet files, which changes what SnipMate globs for and should therefore avoid all these issues. Can people try that branch for a while and post here if any issues arise? Thank you in advance

Hi, I have a similar issue. Snipmate works for a while and at some point tab doesn’t work anymore, I get this:

Error detected while processing function snipMate#TriggerSnippet[50]..snipMate#GetSnippetsForWordBelowCursor:

Closing and reopening vim solves the issue, although it’s quite painful when you are deep into a programming session

I just moved to https://github.com/neoclide/coc.nvim this package and provide many feature . it might help to someone.

I’ve had this issue for several years in both Vim and Neovim.

Workaround

When this bug occurs:

• create a sessionfile within Vim: :mksession!
• then start vim again like: $ vim -S to get back on where you left off.

A restart gets rid of this bug (for a while)

This issue has vexxed me for some time. I tried ‘UltiSnips’ but that Python-based alternative was buggy to the point it was functionally unusable.

This morning I spent some time exploring the SnipMate . E716: Key not present in Dictionary: «get_snippets» . E716: Key not present in Dictionary: «get_snippets» error.

That error originates in the /home/victoria/.vim/bundle/vim-snipmate/autoload/snipMate.vim file. I played with that file; although not a solution, here are my observations — hopefully a developer can debug / fix the code.

:452 in snipMate.vim :

/.vimrc » beginning with # not «, are problematic. In a fresh Vim instance, you can » successfully trigger a snippet in the syntax-incorrect file (preexisting error » in previously saved file). However, when save that tile (Vim `:w` write buffer » command), that save action will trigger a Vim error that appears to cascade » to snipMate: » » Error detected while processing /home/victoria/.vimrc: » line 2: » E488: Trailing characters: apple: # apple » » Under that error condition, you will get the SnipMate » » E716: Key not present in Dictionary: «get_snippets» » » error, and the snippet will show not the snippet name, but whatever » characters you typed prior to pressing , with ‘-1’ appended; e.g., » date-1 | ne-1 | kw-1 | a-1 | m-1 | foo-1 | . » » If you quit Vim, then restart Vim and open a saved

/.vimrc file that » contains the syntax error mentioned above, you can execute the ‘date’ (and » other) snippets — until you save that file, triggering the Vim error » cascade, and the echoing of ‘-1’ appended characters/words, in place of » the intended snippet text. » » NOTES: » 1. debugging: ‘echom’ messages are overwritten; use the more intrusive » but persistent ‘echoe’ » 2. restart Vim to instantiate edits, here » ————————————————————————- » prefer longest word for word in lookups » Victoria — added: echoe ‘word: ‘ word let g:snipMate.word = word for [k,snippetD] in items(funcref#Call(g:snipMate[‘get_snippets’], [snipMate#ScopesByFile(), word])) » Victoria: this is echoed once per snippet match; e.g. if snippets » file has < snippet date | snippet datelong >, will echo 2x » echoe ‘ ****************** ‘ » hack: require exact match if a:exact && k !=# word continue endif call add(matching_snippets, [k, snippetD]) if a:exact break endif endfor endfor return matching_snippets endf»>

Aside: while I very much appreciate the availability, development, and utility of this code, in my opinion, the code is overly-complex: it should simply exact-match the snippet name / word — period.

Источник

Error detected while processing function jedi#init_python #833

Issue

I get the next error when I open a py file at first:

Steps to reproduce

Open a python file.

Your template minimal.vimrc solution is enough to reproduce the error.

Save it as minimal.vimrc in the directory where jedi-vim is installed, cd into that directory, and run Vim with vim -u minimal.vimrc ):

Output of “:verbose JediDebugInfo”

You should run this in a buffer with filetype «python».

Jedi-vim debug information

Using Python version: 3

• global sys.version: 3.2.3 (default, Mar 25 2017, 10:17:28), [GCC 4.7.2]
• global site module: /usr/lib/python3.2/site.py
  ERROR: jedi_vim is not available: SyntaxError: invalid syntax (jedi_vim.py, line 25)
• jedi-vim git version: 0.9.0-21-g84a5299c8f
• jedi git submodule status: bd7c65d9639c2d451d44c6d135b4f6043a918950 pythonx/jedi (v0.12.0)
  6f385bdba182059e0c46917a414981a6d0894527 pythonx/parso (v0.2.1)

Settings

:version

:messages

/pydev/dvrt-tools/dvrt_tools/version_information.py» 487L, 18629C Error detected while processing function jedi#init_python: line 7: Error: jedi-vim failed to initialize Python: jedi#setup_python_imports: could not import jedi_vim: SyntaxError: invalid syntax (jedi_vim.py, line 25). (in function jedi#init_python[3].. 30_init_python[2]..jedi#setup_python_imports, line 30) E475: Invalid argument: @+> E475: Invalid argument: @+> VIM — Vi IMproved 8.1 (2018 May 17, compiled Jun 20 2018 15:20:20) E475: Invalid argument: @+> «various.txt» [readonly] 731L, 28852C «>

Default Python version

The text was updated successfully, but these errors were encountered:

You should run this in a buffer with filetype «python».

Can you please do that?

Ok course :), but I think I did it in ‘python’ buffer, but here is the output

Output of «redir @»> | set filetype | silent verb JediDebugInfo | redir END»

Jedi-vim debug information

Using Python version: 3

• global sys.version: 3.2.3 (default, Mar 25 2017, 10:17:28), [GCC 4.7.2]
• global site module: /usr/lib/python3.2/site.py
  ERROR: jedi_vim is not available: SyntaxError: invalid syntax (jedi_vim.py, line 25)
• jedi-vim git version: 0.9.0-21-g84a5299c8f
• jedi git submodule status: bd7c65d9639c2d451d44c6d135b4f6043a918950 pythonx/jedi (v0.12.0)
  6f385bdba182059e0c46917a414981a6d0894527 pythonx/parso (v0.2.1)

Settings

:version

:messages

/pydev/dvrt-tools/dvrt_tools/version_information.py» 487L, 18629C Error detected while processing function jedi#init_python: line 7: Error: jedi-vim failed to initialize Python: jedi#setup_python_imports: could not import jedi_vim: SyntaxError: invalid syntax (jedi_vim.py, line 25). (in function jedi#init_python[3].. 27_init_python[2]..jedi#setup_python_imports, line 30) filetype detection:ON plugin:ON indent:ON VIM — Vi IMproved 8.1 (2018 May 17, compiled Jun 20 2018 15:20:20) 1:

/.vim/plugin/tagselect.vim 111 more lines 1 more line; before #2 21 seconds ago 112 fewer lines; before #1 24 seconds ago»>

LOL sorry, it was my bad all along, I was probably just having a stroke or something 🙂

I think the problem is that you’re using Python 3.2. Python 3.2 has not been supported for a while. Also note that even Python 3.3 doesn’t get security updates anymore (which we’re also dropping soon).

Hm, and why this error occurred only in last days? I only updated my vim plugins, and I compiled a new vim version. But, I tried to back with vim version, but it did not help.

In this server the python versions have not changed already for long time.

By the way, I tried to use pyenv, but :verbose JediDebugInfo is not be cared this.

And, my default python version is 2.7.3 (if I do not use pyenv).

I have no idea why that occurs just now. The point is that both jedi-vim and Jedi are massively outdated quite a bit plus you’re using a Python version on your system (in VIM) that hasn’t even received security updates for almost two and a half years.

Just upgrade your system.

You have my condolence 😉

Regarding the actual error ( SyntaxError: invalid syntax (jedi_vim.py, line 25) ) however:

1. line 25 indicates that it is Python 2.x
2. but ELLIPSIS = u»…» works in Python 2.7

(tried it using docker run -ti python:3.2 and docker run -ti python:2.7 )

But global sys.version: 3.2.3 (default, Mar 25 2017, 10:17:28), [GCC 4.7.2] indicates that you are using 3.2, where ELLIPSIS = «…» is required instead of ELLIPSIS = u»…» .

I can recommend Arch Linux.. 🙂

Unfortunately, this server is owned by my company (where I am only an employee), and no way to upgrade it :(.
But, I do not understand yet why now this error occurs. I have been used jedi-vim for years in this system.
By the way, it is possible to solve I can use pyenv to workaround python problem? Or any other solution? 🙂

Maybe you can just downgrade jedi-vim? If you’re using an older version it might work again. I’m not saying this is a good idea, since you will be running into new bugs, but I feel like that’s the easiest way to get it running at least partially again.

By the way, it is possible to solve I can use pyenv to workaround python problem?

Not really, because the error already happens in jedi-vim. With the latest versions, this might have helped if the error was in jedi itself. What you could try to do is use the variable force_python_version to use Python 2, that might help.

Downgrade helped me. The d4006ab commit cause the problem if I use minimal.vimrc. With my original vimrc the problem stays.

The force_python_version did not help, the python version stayed 3.2.x.

Источник

Error detected while processing function / Invalid sign text on save #105

On saving/updating of a file I get the following error, the file saves anyway but this is showing up after the save. If I remove vim-signify from my plugins list (I am using spf13) it stops happening, however, this is the coolest plugin in the whole lot so — I do not want go without it 🙂

Error detected while processing function sy#start..sy#highlight#line_disable:
line 15:
E239: Invalid sign text:

The text was updated successfully, but these errors were encountered:

When you start vim what does :set enc? tenc? and :echo has(‘multi_byte’) show?

The problem is that your Vim doesn’t seem to be able to display ‾ , which is the character used for when the first line was removed.

I see 2 possible fixes:

1) Fix your Vim. 🙂 What jamessan said.

2) This is more like a workaround: let g:signify_sign_delete_first_line = ‘x’ (in your vimrc) should work, too.

encoding=latin1
termencoding=
multi_byte shows 1

I am using iterm2 and brew installed vim. I tried vim 7.3 then 7.4 and then 7.4p52 so I don’t think its my vim specifically.

Your 2nd fix made everything better, This issue started after I upgraded my bundles so it might not be playing well with others plugins.

Thanks for the fix, Much apppreciated.

VIM — Vi IMproved 7.4 (2013 Aug 10, compiled Dec 14 2013 18:54:34)
MacOS X (unix) version
Included patches: 1-52
Compiled by Homebrew
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path +mouse_sgr +tag_binary
+autocmd +find_in_path -mouse_sysmouse +tag_old_static
-balloon_eval +float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm -tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent -gettext -mzscheme +textobjects
-clientserver -hangul_input +netbeans_intg +title
+clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand -perl +user_commands
+cmdline_hist +jumplist +persistent_undo +vertsplit
+cmdline_info +keymap +postscript +virtualedit
+comments +langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds +quickfix +wildignore
+cursorshape +localmap +reltime +wildmenu
+dialog_con -lua +rightleft +windows
+diff +menu +ruby +writebackup
+digraphs +mksession +scrollbind -X11
-dnd +modify_fname +signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval +mouse_dec +startuptime -xterm_clipboard
+ex_extra -mouse_gpm +statusline -xterm_save
+extra_search -mouse_jsbterm -sun_workshop -xpm
system vimrc file: «$VIM/vimrc»
user vimrc file: «$HOME/.vimrc»
2nd user vimrc file: «

/.vim/vimrc»
user exrc file: «$HOME/.exrc»
fall-back for $VIM: «/usr/local/share/vim»
Compilation: /usr/bin/clang -c -I. -Iproto -DHAVE_CONFIG_H -DMACOS_X_UNIX -Os -w -pipe -march=native -mmacosx-version-min=10.9 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: /usr/bin/clang -L. -L/usr/local/opt/libyaml/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libksba/lib -L/usr/local/opt/openssl/lib -L/usr/local/lib -Wl,-headerpad_max_install_names -o vim -lm -lncurses -liconv -framework Cocoa -framework Python -lruby.1.9.1 -lobjc -L/Users/josh/.rvm/rubies/ruby-1.9.3-p484/lib

Источник

While using Vim in a Python virtual environment created using the venv module, this error pops up when opening a Python script:

Error detected while processing function jedi#init_python[11]..26_display_exception:
line 19:
Error: jedi-vim failed to initialize Python: jedi#setup_python_imports: ModuleNotFoundError: No module named ‘jedi’ (in function jedi#init_python[4]..26_init_python[27]..jedi#setup_python_imports, li
ne 27). See :messages and/or :JediDebugInfo for more information.

Let’s gather some information about the working environment:

Vim version:

:vers

VIM - Vi IMproved 8.1 (2018 May 18, compiled Mar 19 2020 13:12:18)
Included patches: 1-875, 878, 884, 948, 1046, 1365-1368, 1382, 1401

OS information:

cat /etc/os-release
NAME="Ubuntu"
VERSION="19.10 (Eoan Ermine)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 19.10"
VERSION_ID="19.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan

Current status of the jedi-vim plugin installation:

dpkg -l |grep vim-python-jedi

Package: vim-python-jedi
Version: 0.14.1-1
Priority: optional
Section: universe/python
Source: python-jedi
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Piotr Ożarowski
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 117 kB
Depends: python3-jedi, vim-nox | vim-python
Recommends: vim-addon-manager
Homepage: https://github.com/davidhalter/jedi
Download-Size: 24.0 kB
APT-Manual-Installed: yes
APT-Sources: http://ca.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
Description: autocompletion tool for Python - VIM addon files
Jedi is an autocompletion tool for Python. It works. With and without
syntax errors. Sometimes it sucks, but that's normal in dynamic languages.
But it sucks less than other tools. It understands almost all of the basic
Python syntax elements including many builtins.
.
`vim-addons install python-jedi` will create all needed symlinks in
~/.vim/

Vim plugins using the OS package installer (for Debian/Ubuntu based distros) are handled by the vim-addons utility.

To list all the installed Vim plugins:

vim-addons list


editexisting
espeak
justify
matchit
python-jedi


The version provided by Ubuntu for jedi-vim is older than the latest one publicly available. For more details about the releases: jedi-vim releases

Since version 8, Vim has now a native plugins management.

For more details:


:h packages
:h package-create


To install the vanilla version of jedi-vim and have it available at Vim startup:


unzip -d jedi-vim ~/Downloads/jedi-vim-0.10.0.zip
mkdir -p ~/.vim/pack/vendor/start/jedi-vim
cp -rf jedi/vim/* ~/.vim/pack/vendor/start/jedi-vim/


~./vim/pack/vendor/start is the destination folder for any packages that contain plugins for Vim and automatically enabled at startup.

The plugin is now available and ready to be used in Vim.

If Vim is used in a Python virtual environment, the following error pops up:

jedi-vim: Error when loading the jedi python module (module ‘jedi’ has no attribute ‘__version__’). Please ensure that Jedi is installed correctly (see Installation in the README.

Furthermore, the Python code autocompletion feature provided by jedi-vim is not available in Vim.

2 options are available to fix this issue:

Either install the Python module jedi within the virtual environment using pip

Or re-create the virtual environment and enable access to the system site-packages dir (https://docs.python.org/3.7/library/venv.html) as follows:

python3 -m venv --system-site-packages my_new_env

Enable this new virtual environment:

cd $HOME/my_new_env

If there is anything wrong with loading this module:

Traceback (most recent call last):
File “”, line 1, in
ModuleNotFoundError: No module named ‘jedi’

This module will be picked up from the version installed using the OS package manager. For Ubuntu, jedi is provided by the python3-jedi package.

Published
May 29, 2020May 28, 2020

vim /tmp/somefile

Error detected while processing /usr/share/vim/vim82/suse.vimrc[10]../usr/share/vim/vim82/syntax/syntax.vim[43]..BufRead Autocommands for "*"..script /usr/share/vim/vim82/scripts.vim:
line   30:
E117: Unknown function: dist#script#DetectFiletype
Press ENTER or type command to continue

zypper in vim-data

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com