Package Base Details: python-powerline-git

Git Clone URL: https://aur.archlinux.org/python-powerline-git.git (read-only)
Submitter: Lokaltog
Maintainer: gbs
Last Packager: gbs
Votes: 134
Popularity: 0.002656
First Submitted: 2013-01-23 07:28
Last Updated: 2018-10-10 20:08

Latest Comments

« First ‹ Previous ... 7 8 9 10 11 12

lowfatcomputing commented on 2013-02-21 02:56

I needed to add:

export PYTHONPATH=/usr/lib/python3.3/site-packages

to my /etc/profile for vim.

Lokaltog commented on 2013-02-07 21:43

Thanks, I changed the installation method but forgot to update the PKGBUILD. I'll fix it tomorrow morning.

Anonymous comment on 2013-02-07 21:24

Sorry for the incomplete comment, line 53 should change to:
install -m644 "powerline/bindings/vim/plugin/powerline.vim" "${pkgdir}/usr/share/vim/vimfiles/plugin/powerline.vim"

Anonymous comment on 2013-02-07 21:12

-> Installing fonts...
-> Installing vim plugin...
install: cannot stat ‘powerline/bindings/vim/powerline.vim’: No such file or directory
==> ERROR: A failure occurred in build().

Lokaltog commented on 2013-02-05 13:18

The package checks for Python support if it's installed with e.g. Vundle or without user intervention (see bindings/vim/plugin/source_plugin.vim). But I forgot that the plugin file that's installed with this package doesn't include this check. I don't really think it's an issue, but if it becomes an issue I'll consider including this check in the other plugin file as well (or simply change which plugin file gets installed with this package).

pablox commented on 2013-02-05 02:30

The package never checks for vim python support built on the vim binary. Shouldn't be there on the powerline.vim some:

if has('python') || ('python3')
blabla
endif

¿?

Or it's just assumed because the vim package includes it by default?

Lokaltog commented on 2013-01-24 06:59

Thanks, I'll fix it in a moment.

Anonymous comment on 2013-01-23 23:38

FYI, the PKGBUILD probably wants a "conflicts=('powerline-git')" for people just coming from the old package. As is, pacman doesn't know to uninstall the previous and complains about files already existing in the filesystem.