Package: vim-pathogen
Version: 2.4-1
Severity: minor

While pathogen can be easily installed via package and `vim-addons
install`, that step is *not* sufficient to get a working setup, even
though a symlink is placed in ~/.vim/autoload/. The pathogen.vim does
explain that adding the ``execute pathogen#infect()`` line to one's
.vimrc is necessary, but that's not where I'd usually look.

Please consider either adding a line like this to README.Debian:

| After installation, add the line
| 
|     execute pathogen#infect()
| 
| at the top of your .vimrc.

Alternatively, I think it would be OK if the addon installation actually
added an infect step to VIM's autoload; other plugins become active
after vim-addons install too.


Thanks for maintaining this package
chrysn

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc5+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages vim-pathogen depends on:
ii  vim                2:8.0.0197-2
ii  vim-addon-manager  0.5.6
ii  vim-gtk3 [vim]     2:8.0.0197-2

Versions of packages vim-pathogen recommends:
ii  vim-scripts  20130814

vim-pathogen suggests no packages.

-- no debconf information

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

Attachment: signature.asc
Description: PGP signature

Reply via email to