DOdorianm·Oct 21, 2016
I'm surprised nobody mentioned Vundle: https://github.com/VundleVim/Vundle.vim (13k stars)
In Vim: So long Pathogen, hello native package loadingVundleVim
Vundle.vim
Vim Script2011–2023
VundleVim / Vundle.vim
Vundle.vim
Vundle, the plug-in manager for Vim
39Distinct people
40Mentions
0Explicit recommenders
23.9KGitHub stars
What to know before exploring
What it is
Vundle, the plug-in manager for Vim
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- tpope/vim-fugitive · linked in 3 of the same discussions
- tpope/vim-pathogen · linked in 3 of the same discussions
- kien/ctrlp.vim · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 8:59:20 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year40 dated mentions
Observed mentions: 2011-04-20 19:01:30 UTC to 2023-02-27 19:44:28 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 12 | 0 | 12 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 4 | 1 |
What Hacker News says
4 sourcespackage manager: https://github.com/VundleVim/Vundle.vim
surround: https://github.com/tpope/vim-surround
repeat: http://www.vim.org/scripts/script.php?script_id=2136
git: https://github.com/tpope/vim-fugitive (tim pope plugin)
undo: https://github.com/sjl/gundo.vim
for repls:
https://github.com/jpalardy/vim-slime
for html:
http://emmet.io/
In Ask HN: What are your must-have packages for vim?Reminds me of vim plugin managers like Vundle or NeoBundle. The way they work is you specify a package name and it uses a heuristic to figure out where to look. To steal from the Vundle README...
https://github.com/VundleVim/Vundle.vim
" The following are examples of different formats supported.
" Keep Plugin commands between vundle#begin/end.
" plugin on GitHub repo
Plugin 'tpope/vim-fugitive'
" plugin from http://vim-scripts.org/vim/scripts.html
Plugin 'L9'
" Git plugin not hosted on GitHub
Plugin 'git://git.wincent.com/command-t.git'
" git repos on your local machine (i.e. when working on your own plugin)
Plugin 'file:///home/gmarik/path/to/plugin'
" The sparkup vim script is in a subdirectory of this repo called vim.
" Pass the path to set the runtimepath properly.
Plugin 'rstacruz/s
Read the rest
parkup', {'rtp': 'vim/'}
" Avoid a name conflict with L9
Plugin 'user/L9', {'name': 'newL9'}
It's one of those things that works so well you can just kind of forget about it once you get used to it, but you're not really locked in either.