Bug 1186344 - vim-plugin-powerline does not work
Summary: vim-plugin-powerline does not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: powerline
Version: 21
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1133229
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-27 13:37 UTC by Brad Hubbard
Modified: 2015-02-06 21:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1133229
Environment:
Last Closed: 2015-02-06 21:14:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brad Hubbard 2015-01-27 13:37:57 UTC
+++ This bug was initially created as a clone of Bug #1133229 +++

Description of problem:
powerline.vim is installed into the wrong folder

it should be installed to '/usr/share/vim/vimfiles/plugins'
and depand on vim-filesystem


Version-Release number of selected component (if applicable):
0.0.1-7.20140508git9e7c6c.fc20


How reproducible:
always


Steps to Reproduce:
1. install vim-plugin-powerline
2. open vim
3. 

Actual results:
powerline-plugin not loaded

Expected results:
powerline plugin loaded


Additional info:
maybe the vim relating files from powerline-package should be moved (not copyed) to the vim-plugn-powerline-package

--- Additional comment from Andreas Schneider on 2014-08-26 09:01:07 EDT ---

The problem is that the upstream installation script does not correctly install these file. Also all the bindings are in the wrong directory.

/usr/lib/python2.7/site-packages/powerline/bindings/vim
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.py
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.pyc
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.pyo
/usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin
/usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin/powerline.vim

same for the bash files:

/usr/lib/python2.7/site-packages/powerline/bindings/bash
/usr/lib/python2.7/site-packages/powerline/bindings/bash/powerline.sh


Could you please open a upstream bug that the location of the bindings gets fixed! I will then create a new package. I just don't have time to look into this myself.

--- Additional comment from Brad Hubbard on 2015-01-05 18:13:26 EST ---

Seems to be the same issue for the tmux-powerline package?

Comment 1 Brad Hubbard 2015-01-27 13:40:52 UTC
Same problem exists in f21.

$ rpm -qa \*powerline\*
tmux-powerline-1.3.1-2.fc21.noarch
vim-plugin-powerline-1.3.1-2.fc21.noarch
powerline-1.3.1-2.fc21.x86_64

$ find /usr/lib/python2.7/site-packages/powerline/bindings/vim
/usr/lib/python2.7/site-packages/powerline/bindings/vim
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.pyo
/usr/lib/python2.7/site-packages/powerline/bindings/vim/autoload
/usr/lib/python2.7/site-packages/powerline/bindings/vim/autoload/powerline
/usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.py
/usr/lib/python2.7/site-packages/powerline/bindings/vim/__init__.pyc

$ find /usr/lib/python2.7/site-packages/powerline/bindings/tmux
/usr/lib/python2.7/site-packages/powerline/bindings/tmux
/usr/lib/python2.7/site-packages/powerline/bindings/tmux/__init__.pyo
/usr/lib/python2.7/site-packages/powerline/bindings/tmux/__init__.py
/usr/lib/python2.7/site-packages/powerline/bindings/tmux/__init__.pyc

Comment 2 Andreas Schneider 2015-01-27 14:09:48 UTC
Brad, what is the error you get?

The files are in the right directory:

magrathea:~ # python
>>> import powerline.bindings.vim
>>>

If you move or delete them you will get an error if you try to import them.

Comment 3 Brad Hubbard 2015-01-27 15:10:45 UTC
Yesterday I had powerline in tmux and vim. Last night I upgraded to the latest f21 packages. Today I have no powerline in vim or tmux or at least nothing I recognise as powerline. There is no error that I can see so far.

"vim -V" shows the following...
Searching for "/usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin/**/*.vim"

$ ls /usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin/**/*.vim
ls: cannot access /usr/lib/python2.7/site-packages/powerline/bindings/vim/plugin/**/*.vim: No such file or directory

i have not moved or deleted anything AFAIK.

Comment 4 Andreas Schneider 2015-01-30 08:18:30 UTC
Can you retry with version 2.0. It is in stable now ...

I wonder what code searches for *.vim. I didn't find something in the source code. Only the tests ...

Comment 5 Brad Hubbard 2015-01-30 14:15:17 UTC
I'll try to get to this today otherwise it will be a few days as I am travelling.

Comment 6 Brad Hubbard 2015-02-03 21:52:13 UTC
There's no change for me with version 2.0. Still getting the results in comment 3 and no recognisable powerline in tmux or vim. I'll look into this further when I get a chance but that probably won't be for a couple of weeks.

Comment 7 Brad Hubbard 2015-02-04 22:43:55 UTC
Okay. I did something stupid when I upgraded and did not include the plugins. Once I did that I chased down why it was looking where it was looking for the plugins and here is the fix for me.

Vim:

Change in ~/.vimrc

"set rtp+=/usr/lib/python2.7/site-packages/powerline/bindings/vim
set rtp+=/usr/share/vim/site/

Tmux:

Change in ~/.tmux.conf

#source /usr/lib/python2.7/site-packages/powerline/bindings/tmux/powerline.conf
source /usr/share/tmux/powerline.conf

I guess the problem here is that the plugins moved from /usr/lib/python2.7/site-packages to /usr/share/vim/ and /usr/share/tmux.

Sorry if this was harder than it should have been Andreas and thanks for your work with these packages.

Comment 8 Brad Hubbard 2015-02-06 21:14:26 UTC
Closing as NOTABUG


Note You need to log in before you can comment on or make changes to this bug.