MKmklein994·Nov 9, 2017
Yeah:
:PlugUpdate
See https://github.com/junegunn/vim-plug
EDIT: formatting
In Neovim v0.2.1 releasedjunegunn
vim-plug
Vim Script2014–2022
junegunn / vim-plug
vim-plug
:hibiscus: Minimalist Vim Plugin Manager
22Distinct people
24Mentions
1Explicit recommenders
35.8KGitHub stars
What to know before exploring
What it is
:hibiscus: Minimalist Vim Plugin Manager
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
The first thing I would recommend you is to build the vimrc yourself. Forget about the huge github vimrcs available out there. Check them out and see if there are things you…
farresito used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- preservim/nerdtree · linked in 2 of the same discussions
- vim-polyglot/vim-polyglot · 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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:01:02 AM 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 year24 dated mentions
Observed mentions: 2014-09-11 10:53:48 UTC to 2022-10-12 04:25:39 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 |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 5 | 2 | 3 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesFor an easy start, use a sane defaults plugin like sensible.vim [1] or vim-simple-defaults [2] (more opiniated).
Also, use vim-plug [3] with few plugin like ctrlp, nerdtree, nerdcommenter and vim-simple-complete [4].)
[1] https://github.com/tpope/vim-sensible
[2] https://github.com/maxboisvert/vim-simple-defaults
[3] https://github.com/junegunn/vim-plug
[4] https://github.com/maxboisvert/vim-simple-complete
I am the author of [2] and [4].
In Getting started with vimI am sorry for that issue, and sorry for all the emails,but SpaceVim is not only copy the name of spacemacs,it has many important ideas of spacemacs, such as layers(plugin and config groups), leader guide,and mappings fuzzy searching.
why I create SpaceVim, instead of support space-vim, I think space-vim is just a copy of https://github.com/ctjhoa/spacevim and https://github.com/Tehnix/spaceneovim-layers and https://github.com/Tehnix/spaceneovim
BTW space-vim's some syntax script is copy from https://github.com/junegunn/vim-plug and install script is just copy from spf13.
so I do not want to support it, but when I create SpaceVim, and post blog anout SpaceVim, the author of space-vim comments a lot of unfriendly message.
and here is the link.
so I will apologies to all the people who receive my emails about SpaceVim, but I will not apolo
Read the rest
gies to the author of space-vim.
I now use https://github.com/junegunn/vim-plug - you can setup a one-liner in your Vimrc to download and set it up, then :PlugInstall and you're done (similar to what they have in the readme but I linked to a specific hash on GitHub instead of master).
I also keep a separate file that lists the plugins to install and the source that from my main .vimrc. A lot of my coworkers have wanted my main vimrc for an "out of the box setup" of Vim and found it best for them to specify their own plugins rather than just blindly use mine - it also makes it easier for them to grab the latest copy without any conflicts.
In Using tmux properly