Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / lambdalisue/vim-pyenv issues and pull requests

#33 - PYENV_VERSION affect to the :terminal

Issue - State: closed - Opened by kyoh86 over 5 years ago - 3 comments
Labels: bug

#32 - Use jedi parameter instead of dropped function.

Pull Request - State: closed - Opened by kyoh86 about 6 years ago - 1 comment

#31 - Still not able to get it work.

Issue - State: open - Opened by frank777777777 about 6 years ago - 2 comments

#30 - Correctly check python2 in NeoVim

Pull Request - State: closed - Opened by oblitum about 6 years ago - 1 comment

#29 - Merged pull request #28 cause error on NeoVim

Pull Request - State: closed - Opened by oblitum over 6 years ago - 2 comments

#28 - Fixes issue #23 with dynamic python 2 & 3 support.

Pull Request - State: closed - Opened by foxwoods369 over 6 years ago - 11 comments

#27 - pyenv not activating with :py3

Issue - State: closed - Opened by justin8 almost 7 years ago - 6 comments

#26 - very slow start time?

Issue - State: open - Opened by dmitry-saritasa about 7 years ago - 1 comment

#25 - Don't try to activate "system" pyenv

Issue - State: open - Opened by z0rc over 7 years ago - 3 comments

#24 - RFC: Provide API methods for Python 2 & 3

Issue - State: open - Opened by jalcine over 7 years ago - 3 comments

#22 - Error detected while processing function pyenv#activate

Issue - State: closed - Opened by oblitum over 7 years ago - 20 comments

#21 - Python3

Issue - State: closed - Opened by iho over 7 years ago - 3 comments

#20 - Fix typo

Pull Request - State: closed - Opened by ryunix over 8 years ago - 1 comment

#19 - RFC: Shouldn't vim-pyenv depends on vim's compile options?

Issue - State: open - Opened by takegue over 8 years ago - 6 comments
Labels: enhancement

#17 - 'initialize.py' conflicts with jedi when dein.vim is used.

Issue - State: open - Opened by lambdalisue over 8 years ago - 1 comment
Labels: bug

#16 - PyenvActivate activate invalid python

Issue - State: closed - Opened by lambdalisue over 8 years ago

#15 - How to automatically pickup a python version with autocmd

Issue - State: closed - Opened by owais almost 9 years ago - 12 comments
Labels: question

#14 - Error detected while processing function pyenv#activate

Issue - State: closed - Opened by samuell about 9 years ago - 6 comments

#14 - Error detected while processing function pyenv#activate

Issue - State: closed - Opened by samuell about 9 years ago - 6 comments

#13 - Error running PyenvActivate

Issue - State: closed - Opened by oblitum about 9 years ago - 12 comments

#13 - Error running PyenvActivate

Issue - State: closed - Opened by oblitum about 9 years ago - 12 comments

#12 - typo in README example

Pull Request - State: closed - Opened by tony over 9 years ago - 1 comment

#11 - Add ctags for active environment

Issue - State: closed - Opened by razor-x over 9 years ago - 7 comments
Labels: enhancement

#10 - Cannot use vim-pyenv-(de)activate-post hooks.

Issue - State: closed - Opened by razor-x over 9 years ago - 6 comments

#9 - Aggressive refactoring

Pull Request - State: closed - Opened by lambdalisue over 9 years ago

#9 - Aggressive refactoring

Pull Request - State: closed - Opened by lambdalisue over 9 years ago

#8 - vim-pyenv updates PYTHONPATH, but vim still uses system python

Issue - State: closed - Opened by alexhbnr over 9 years ago - 1 comment
Labels: invalid, question

#8 - vim-pyenv updates PYTHONPATH, but vim still uses system python

Issue - State: closed - Opened by alexhbnr over 9 years ago - 1 comment
Labels: invalid, question

#7 - vim-pyenv prepends Python 3 sys.path in Python 2 Vim

Issue - State: closed - Opened by blueyed almost 10 years ago - 3 comments
Labels: bug, question

#7 - vim-pyenv prepends Python 3 sys.path in Python 2 Vim

Issue - State: closed - Opened by blueyed almost 10 years ago - 3 comments
Labels: bug, question

#6 - g:pyenv#force_py_version documented, but not used

Issue - State: closed - Opened by blueyed almost 10 years ago - 3 comments
Labels: enhancement

#6 - g:pyenv#force_py_version documented, but not used

Issue - State: closed - Opened by blueyed almost 10 years ago - 3 comments
Labels: enhancement

#5 - doc: fixes while reading it

Pull Request - State: closed - Opened by blueyed almost 10 years ago - 3 comments

#5 - doc: fixes while reading it

Pull Request - State: closed - Opened by blueyed almost 10 years ago - 3 comments

#4 - Accelerate startingtime

Issue - State: closed - Opened by lambdalisue about 10 years ago
Labels: enhancement

#4 - Accelerate startingtime

Issue - State: closed - Opened by lambdalisue about 10 years ago
Labels: enhancement

#3 - Install instructions for vundle

Issue - State: closed - Opened by samuell over 10 years ago - 3 comments
Labels: enhancement, question

#3 - Install instructions for vundle

Issue - State: closed - Opened by samuell over 10 years ago - 3 comments
Labels: enhancement, question

#2 - Fixed issue#1

Pull Request - State: closed - Opened by lambdalisue over 10 years ago

#1 - homebrew installed pyenv could not be recognized

Issue - State: closed - Opened by lambdalisue over 10 years ago

#1 - homebrew installed pyenv could not be recognized

Issue - State: closed - Opened by lambdalisue over 10 years ago