Issues filed for tpope/vim-pathogen

View Full Project
Do you use vim-pathogen? Leave a review!

Rate of open issues in the last 60 days

vim-pathogen open issues (View Closed Issues)
  • over 1 year stopped working
  • almost 2 years Adding individual plugin to runtimepath
  • almost 2 years :V* commands blocking tab complete
  • over 2 years vim startup statistics
  • over 3 years Pathogen causing vim to crash
  • almost 4 years Using pathogen in Windows from a SMB Share
  • about 4 years _call_ vs _execute_ _pathogen#infect()
  • about 4 years whitelist plugins
  • over 4 years Common configuration issue with Pathogen
  • over 4 years Pathogen not loading plugins on Arch Linux
  • almost 5 years Pathogen doesn't work with UNC paths on Windows
  • over 5 years Is there a way of adding a specific addon after vim is already started?
  • over 6 years provide standard reload mapping
  • over 6 years Incompatible with OmniCppComplete
  • almost 7 years Subdirectories of bundles are not parsed for addition to rtp
  • over 7 years ShowMarks when managed by Pathogen sets vim running at ~90% CPU when a :help 'topic' command is issued

vim-pathogen closed issues

  • almost 2 years Do not recommend the use unauthenticated git cloning
  • almost 2 years Pathogen override (or break) commands like tabstop tabwith
  • about 2 years Does not work on windows and vim 7.4
  • about 2 years Using plugins globally
  • over 2 years Reload every plugin as in vim-scriptease
  • over 2 years vim freeze for a couple second
  • over 2 years Swift support
  • over 2 years Pathogen doesn't put bundles in runtimepath
  • over 2 years plugins not loading
  • over 2 years curl: (7) Failed to connect to tpo.pe port 443: Network is unreachable
  • over 2 years Commit e2f96de (Experimental: Support "vimfiles" subdirectory) broke snipmate
  • over 2 years using pathogen on Vim 7.0 hangs, export VIMBLACKLIST=Y is required
  • over 2 years Pathogen doesn't work on Debian Jessie
  • over 2 years E117 while saving the *.go src files
  • almost 3 years Spread the vimrc
  • almost 3 years https://tpo.pe/pathogen.vim NOT FOUND error
  • almost 3 years curl error
  • about 3 years pathogen#surround(...) produces extra / if used without {}
  • about 3 years Question about using Pathogen on specific sub-directories
  • over 3 years ck runtimepath
  • over 3 years Pathogen does not work, when settings made in _gvimrc
  • over 3 years syntax error in .vimrc for pathogen
  • over 3 years Pathogen not loading bundles on OSX
  • over 3 years ~/.vim/after not last in &rtp
  • over 3 years vim-easymotion not installing through pathogen
  • over 3 years Remove scriptease commands
  • over 3 years support for pythonx-directory (neovim)
  • over 3 years Echos 4 1 when opening vim
  • almost 4 years Unable to load plugins on Ubuntu trusty64
  • almost 4 years Download of pathogen fails (curl SSL: certification verification failed)
  • almost 4 years Another lockup on ancient Vim
  • about 4 years E149: Sorry, no help for PluginName.
  • about 4 years How to test if pathogen is installed
  • about 4 years Filetype cycling breaks md detection
  • about 4 years Wrong URL?
  • about 4 years Issue:Error detected while processing function 3..13..14 on my mac
  • about 4 years 2.3 tag missing
  • about 4 years Can't load plugins documentations using :Helptags
  • about 4 years Link problem in README.md (?)
  • over 4 years Old versions of vim hang on start unless $VIMBLACKLIST is non empty
  • over 4 years Bad filenames with bad UTF-8 chars cause errors
  • over 4 years Question: Why execute instead of call?
  • over 4 years :make fails on file names containing spaces
  • over 4 years Closing latex environments
  • over 4 years support for definition lists?
  • over 4 years Pathogen not loading plugins
  • over 4 years runtime plugin loading
  • almost 5 years dot named directories in bundle not added to rtp
  • almost 5 years runtimepath correct but plugins not working