You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your update on this bug. I know this is a bit of a hassle but can you please submit the output of your bug report as suggested in our troubleshooting session?
I could not reproduce your bug. Removed the linter and had no troubles whatsoever.
I have the same problem. Installed it with vim-plug. NVIM v0.2.3-820-g9cefd83cc. Build type: RelWithDebInfo. MX-Linux 17.
Error detected while processing function pymode#buffer_post_write[10]..pymode#lint#check[11]..provider#python3#Call:
line 18:
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/BigHome/Dropbox/dotfiles/nvim/python/python-plugins/python-mode/pymode/lint.py", line 46, in code_check
options.linters_params['pylint']['clear_cache'] = True
KeyError: 'pylint'
No, this was not addressed in #864 and it was not fixed. In the mentioned issue the "solution" was to use pathogen instead of vim-plug. You can't force your users to a specific plugin manager.
Hi @amireldor I tought it was fixed, my mistake. I don't think you need to be that aggressive ... I'm not trying to force anyone to nothing ok? Still, please consider that I'm just a volunteer on the project.
I'm glad you could make it work with your desired tools and it would be nice if you send us a PullRequest with the proper improvement on the project documentation.
If you do so, please try to "link" this issue and also #864 on the commit message in order to keep the correct track of information.
@diraol please accept my apology. Sometimes when I use Vim too much without looking out of the window at the birds I forget my manners. I'll do my best to make a PR today. Thanks.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
fmv1992 commentedon Mar 10, 2018
Hey @guoang,
Thanks for your update on this bug. I know this is a bit of a hassle but can you please submit the output of your bug report as suggested in our troubleshooting session?
I could not reproduce your bug. Removed the linter and had no troubles whatsoever.
Best,
fmv1992 commentedon Mar 10, 2018
Actually I missed the point that you were referring to the master branch.
Our master branach is super outdated. I should point it out in our documentation.
Do not close this issue! : )
alienbogart commentedon Mar 12, 2018
I have the same problem. Installed it with vim-plug.
NVIM v0.2.3-820-g9cefd83cc. Build type: RelWithDebInfo. MX-Linux 17.diraol commentedon Mar 17, 2018
This was addressed on #864 (and is already fixed).
amireldor commentedon Mar 31, 2018
No, this was not addressed in #864 and it was not fixed. In the mentioned issue the "solution" was to use pathogen instead of vim-plug. You can't force your users to a specific plugin manager.
amireldor commentedon Mar 31, 2018
With vim-plug, I specified the 'develop' branch and now stuff works.
diraol commentedon Mar 31, 2018
Hi @amireldor I tought it was fixed, my mistake. I don't think you need to be that aggressive ... I'm not trying to force anyone to nothing ok? Still, please consider that I'm just a volunteer on the project.
I'm glad you could make it work with your desired tools and it would be nice if you send us a PullRequest with the proper improvement on the project documentation.
If you do so, please try to "link" this issue and also #864 on the commit message in order to keep the correct track of information.
amireldor commentedon Mar 31, 2018
@diraol please accept my apology. Sometimes when I use Vim too much without looking out of the window at the birds I forget my manners. I'll do my best to make a PR today. Thanks.
diraol commentedon Mar 31, 2018
No problem @amireldor, and thanks for the PR! Welcome to the project! ;)
stale commentedon Aug 28, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Sep 18, 2018
Closed due to inactivity.