HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
junegunn
vim-plug
Vim Script2014–2022
junegunn / vim-plug

vim-plug

:hibiscus: Minimalist Vim Plugin Manager

22Distinct people
24Mentions
1Explicit recommenders
35.8KGitHub stars
REPOSITORY AT A GLANCE

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

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, 3:30:57 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.

0123452014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC523
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC422
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC404
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC404
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

4 sources
I'm relatively new to Vim (~4 months). I used the "learning by doing" approach by forcing myself to use Vim to write C and Python at work. I had two main reasons for learning Vim: (1) Vim is everywhere, so it must be worth it to learn the basics at least; and (2) modal editing felt easier on my wrists than the standard mouse + shortcuts approach I ended up using in other IDEs. Here is my advice: 1. Start with only a theme in your .vimrc, so no plugins or non-standard key bindings. 2. Use Vimtutor (or any other tutorial) to learn the basics: normal vs. insert mode, movement, manipulation, yank/paste (+ clipboard), splits, buffers, and searching. 3. As you write code, you will find yourself wanting to know how to do X. This is where Google and a simple "cheatsheet" file come in. Once you find out how to do X via Google, add an entry to your
Read the rest
cheatsheet file (example in HTML form: [1]). 4. In many cases, you will find that a plugin will solve one of your issues. Install that plugin and add it to your .vimrc. I recommend vim-plug[2] for managing and installing plugins. 5. There are many useful plugins out there. Two I would strongly recommend: CtrlP[3] and NERDTree[4]. Once you have a good grasp of Vim, I would recommend exploring Emacs + Evil-mode if you want a more complete IDE experience. [1]: https://assil.me/2018/11/12/vim-cheatsheet.html [2]: https://github.com/junegunn/vim-plug [3]: https://github.com/kien/ctrlp.vim [4]: https://github.com/scrooloose/nerdtree
In Absolute Beginner's Guide to Emacs (2012)
The Emacs package list has a description field on the right, a shortcut for more info (?) and after it's installed you've got C-h m and often info pages (C-h i). What's wrong with that? Vim has no unified plugin structure, there are several plugin manager packages (often installed via git clone). I personally use vim-plug[i] which is more on the minimal side, but there are others like pathogen or vundle. No real centralized plugin repository like melpa, I don't think one of the plugin managers I've used had some kind of common install-screen. You mostly enter the github address and execute the package update vimscript. I've seen more Emacs info packages than :help docs, but in most cases I'm browsing the githup README.md/.org anyways. [1]: https://github.com/junegunn/vim-plug
In Vim plugins I use
Here are some I find invaluable: * FZF. Perhaps the best fuzzy finder for Vim https://github.com/junegunn/fzf/ * ALE. Asynchronous Linting Engine, totally awesome. https://github.com/w0rp/ale * Polyglot. A "best of" language pack. https://github.com/sheerun/vim-polyglot * Plug. IMHO the best plugin manager going https://github.com/junegunn/vim-plug. * Fugitive. The best git wrapper there is https://github.com/tpope/vim-fugitive * vim-test. A plugin that helps you run tests from inside of Vim. https://github.com/janko-m/vim-test Outside of that, switch to NeoVim if you haven't already (https://neovim.io/). Or give Oni a chance, it looks really promising (https://www.onivim.io/).
In Vim plugins I use
I was operating under the impression that a single asterisk would muck up the Markdown parsing on HN. Turns out I'm half wrong it seems. Some work. With the italicised tests below, the first has a prepended asterisk, the second has an appended one. * Test Test* Test Test Test * I think I just started using daggers because U+2020 was super easy to remember and to avoid Markdown issues and the habit has stuck. You don't by any chance use Vim, do you? I use the Unicode plugin[0] by Christian Brabandt in Vim to quickly search for Unicode characters. You can use vim-plug[1][2] by Junegunn Choi, for instance, to install it and keep it updated or just install it manually yourself. call plug#begin('~/.vim/plugged') Plug 'https://github.com/chrisbra/unicode.vim' call plug#end() Then within vim type :UnicodeSearch dagger to search for d
Read the rest
aggers. This gives me: † U+2020 Dec:008224 DAGGER (/-) † ‡ U+2021 Dec:008225 DOUBLE DAGGER (/=) ‡ ‡ ⸶ U+2E36 Dec:011830 DAGGER WITH LEFT GUARD ⸶ ⸷ U+2E37 Dec:011831 DAGGER WITH RIGHT GUARD ⸷ ⸸ U+2E38 Dec:011832 TURNED DAGGER ⸸ U+1F5E1 Dec:128481 DAGGER KNIFE 🗡 [0] https://github.com/chrisbra/unicode.vim [1] https://github.com/junegunn/vim-plug [2] https://github.com/junegunn/vim-plug/wiki/tips#automatic-ins...
In ITER is a showcase for the drawbacks of fusion energy

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.