-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with ncm2_tmux, constant errors on autocomplete #347
Comments
The exception message doesn't seem to be complete. What's the result of Possibly related to ncm2/ncm2-tmux#2 |
I have pushed an update. Please test the latest ncm2-tmux |
same issue |
I'm sorry I didn't answer in time. I updated space-vim, all plugins and the jedi python package in my Virtualenv, and the first problem was fixed, I then installed tmux and that solved a similar error message that I got right after. Thanks a lot for your help! |
Environment
Put the contents of
:version
below:Problem Description
Getting an error with the latest version while having ncm2_tmux@yarp enabled by default. Disabling it (by exclusion of ncm2/ncm2-tmux) fixes the problem.
[ncm2_tmux@yarp] error caught in notification handler 'on_complete [{'filepath': '/home/rafa/www/espaciopla/web/espaciopla/models.py', 'typed': ' date', 'scope_match': '', 'startccol': 5, 'scope_level': 1, '
word_pattern': '(-?\d*\.\d\w*)|([^\\`\\~\\!\\@\\#\\$\\%\\^\\&\\*\\(\\)\\-\\=\\+\\[\\{\\]\\}\\\\\\|\\;\\:\\\'\\"\\,\\.\\<\\>\\/\\?\\s]+)', 'time': 1532909776.5298116, 'lnum': 24, 'bufnr': 12, 'changedtick':
1120, 'manual': 0, 'base': 'date', 'ccol': 9, 'filetype': 'python', 'curpos': [0, 24, 9, 0, 9], 'tick': [[0, 24, 9], 0], 'early_cache': False, 'context_id': 721, 'scope': 'python', 'matcher': {'name': 'abbrfuzz
y'}, 'source': {'subscope_enable': 0, 'early_cache': 0, 'name': 'tmux', 'priority': 4, 'enable': 1, 'on_warmup': 'ncm2_tmux#on_warmup', 'ready': 1, 'mark': 'T', 'auto_popup': 1, 'on_complete': 'ncm2_tmux#on_com
plete', 'on_completed': 'ncm2_tmux#on_completed'}, 'bcol': 9, 'match_end': 4}]'
Thank you!!
The text was updated successfully, but these errors were encountered: