lambdalisue / lambdalisue/vim-pyenv
'initialize.py' conflicts with jedi when dein.vim is used.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Vim Script
- Stars
- 107
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When dein.vim is used, initialize.py of vim-pyenv conflicts with that of jedi.vim.
It could be solved by using lazy loading but the filename should be changed to support all users.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate initialize.py and inspect how vim-pyenv loads it alongside dein.vim and jedi.vim. Update the conflicting filename and any references, then verify that vim-pyenv works when both plugins are enabled without loading conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vim
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100