Repository navigation
Closed
Labels
Description
Just pulled the new release (on develop branch). Using vim 7.4 (including patches 1-5), python 2.7.
After tackling python-mode backward-incompatibilities ( ok you are the maintainer :-) ) vim starts fine.
First time calling PymodeLint works fine too, second time not (no changes were done to the file, or any of the settings). Vim complains about undefined variables.
output of vim :messages
Error detected while processing function pymode#lint#check:
line 21:
E121: Undefined variable: b:pymode_signs
E15: Invalid expression: b:pymode_signs
line 26:
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
E121: Undefined variable: b:pymode_signs
E116: Invalid arguments for function add
line 32:
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
E121: Undefined variable: b:pymode_errors
Error detected while processing function pymode#lint#check..pymode#lint#show_errormessage:
line 1:
E121: Undefined variable: b:pymode_errors
E116: Invalid arguments for function empty(b:pymode_errors)
E15: Invalid expression: empty(b:pymode_errors)
line 10:
E121: Undefined variable: b:pymode_errors
E116: Invalid arguments for function has_key(b:pymode_errors, l)
E15: Invalid expression: has_key(b:pymode_errors, l)
output off :call pymode#troubleshooting#test()
Pymode diagnostic
===================
VIM:704, OS: Linux, multi_byte:1, pymode: 0.7.1b, python: python
VIM python paths:
-----------------
<skipped>
Pymode variables:
-------------------
let pymode = 1
let pymode_breakpoint = 1
let pymode_breakpoint_bind = '<leader>b'
let pymode_doc = 1
let pymode_doc_bind = '<leader>k'
let pymode_folding = 1
let pymode_indent = 1
let pymode_lint = 1
let pymode_lint_checkers = ['pyflakes', 'pep8', 'pep257', 'mccabe']
let pymode_lint_cwindow = 1
let pymode_lint_ignore = 'C0110'
let pymode_lint_message = 1
let pymode_lint_on_fly = 0
let pymode_lint_on_write = 0
let pymode_lint_select = ''
let pymode_lint_signs = 1
let pymode_motion = 1
let pymode_options = 1
let pymode_paths = []
let pymode_quickfix_maxheight = 6
let pymode_quickfix_minheight = 3
let pymode_rope = 1
let pymode_run = 1
let pymode_run_bind = '<leader>run'
let pymode_trim_whitespaces = 1
let pymode_virtualenv = 1
let pymode_virtualenv_enabled = 'confidential'
let pymode_virtualenv_path = 'confidential'
Activity
klen commentedon Dec 2, 2013
Please try version from develop.
lodagro commentedon Dec 2, 2013
That is the version i`m using.
klen commentedon Dec 2, 2013
I just updated the repository 20 minutes ago and there not no occurrences of the word 'pymode_errors'
lodagro commentedon Dec 2, 2013
Ok, i pulled in latest changes to develop and no longer get the vim-messages. However the sing placement is incorrect now, they are added to the left most split when using multiple splits. After running PyModeLint, the cursor also jumps to the leftmost split.
klen commentedon Dec 2, 2013
I pushed some updates. Try to current develop version.
lodagro commentedon Dec 2, 2013
Signs are ok again. Cursor still jumps to left most split.
klen commentedon Dec 2, 2013
What do you mean "Cursor jumps"? I open several files in vertical and horizontal splits and try to run code checking with different ways. Cursor stays in the current window.
I added
debug.vimto repository, could you load vim with only pymode likevim -u <path_to_pymode>/debug.vimand check for the problem still exists. Because I cannot repeat.lodagro commentedon Dec 2, 2013
Using
debug.vimi can not reproduce either.Without the
debug.vimway of startup, i have the issue in conjunction with the vim-plugin majutsushi/tagbar. The left most split is a special kind of window that is used by the tagbar plugin to display the tags in the current buffer. Before the python-mode upgrade i never saw the issue of the cursor moving from the buffer used to run python-mode linting to jump to the tagbar split, when linting completed.klen commentedon Dec 2, 2013
I also use
tagbar.vim. I update tagbar to last version and move them to left side, open several python files in vertical splits and also make code checking, but cursor stay on the place.I maked small fix in current develop branch just now, maybe it can help.
lodagro commentedon Dec 2, 2013
Upgraded both tagbar and python-mode. Cursor still jumps. It appears to jump only when there is a linting violation and if it is not the first time linting results in an error.
fyi, below are the tagbar settings i have in my .vimrc
klen commentedon Dec 2, 2013
I still cannot repeat, but maybe current updates helps.
lodagro commentedon Dec 2, 2013
Unfortunately not.
klen commentedon Dec 2, 2013
Should be fixed in current develop branch.
lodagro commentedon Dec 3, 2013
👍
Thanks!