MIminusf·Dec 23, 2017
i find unite.vim very useful
https://github.com/Shougo/unite.vim
In Intermediate Vim tipsShougo
unite.vim
Vim Script2013–2017
Shougo / unite.vim
unite.vim
:dragon: Unite and create user interfaces
8Distinct people
9Mentions
0Explicit recommenders
2.8KGitHub stars
What to know before exploring
What it is
:dragon: Unite and create user interfaces
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
- kien/ctrlp.vim · linked in 2 of the same discussions
- shougo/vimproc.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, 3:56:07 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 year9 dated mentions
Observed mentions: 2013-08-29 22:30:24 UTC to 2017-12-23 11:22:15 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 |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
9 sourcesJust a small sampling of what's out there that could search just as well or better:
For emacs:
helm-ack[1]
helm-ag[2]
helm-git-grep[3]
For vim:
ctrlp[4]
unite[5]
[1] - https://github.com/syohex/emacs-helm-ack
[2] - https://github.com/syohex/emacs-helm-ag
[3] - https://github.com/yasuyk/helm-git-grep
[4] - https://github.com/kien/ctrlp.vim
[5] - https://github.com/Shougo/unite.vim
In Poll: What is your primary editor?Why do you advocate using vim in a terminal?
I prefer unite[1] to ctrl-p[2], it's much more flexible.
1: https://github.com/Shougo/unite.vim
2: https://github.com/kien/ctrlp.vim
In Vim After 11 Years (2013)Unite[0] and Vimfiler[1] for Vim. Before, searching with ag[2] required using the command line, now I can do it directly from Vim. Also, opening NERDTree took seconds, vimfiler opens in less than a second.
[0] https://github.com/Shougo/unite.vim
[1] https://github.com/Shougo/vimfiler.vim
[2] https://github.com/ggreer/the_silver_searcher
In Ask HN: What are your essential tools you wish you had discovered sooner?I can't believe how far vim plugins have come in past couple of years. If you haven't looked at new vim plugins in while take a look at
https://github.com/Shougo/unite.vim
https://github.com/Shougo/neocomplcache.vim
https://github.com/bling/vim-airline
In tpope's Vim Config and Plugins — NYC Vim MeetupWTF are you talking about? Vim have may have many demerits but segfaults is not on that list. If segfaults are that frequent you described then people would have jumped ship already.
I can't comment on the code structure of Vim but it does not matter to me because end product is working fine for me for 5+ years. Also bad code structure did not stop continuous development of Vim. Just for example there were 1000 patches added to the core before Vim version was changed from 7.3 to 7.4 within 2 years. Important features like more python binding, lua bindings were added during this time. Even if you see the current patch log of 7.4 ftp://ftp.vim.org/pub/vim/patches/7.4/README 68 patches were added since 7.4 release.
Though async future is not built-in there are several plugins for doing async operation, for example vim-dispatch[1] and vimproc
Read the rest
. Vimproc is more widely used. See Unite.vim[3] , neocomplete[4], VimShell[5] for demonstration. I would specially point to VimShell because with the help of it you can run REPL inside Vim and pass buffer content to it. Also there is YouCompleteMe[6] which provides FAST autocomplete.
[1](https://github.com/tpope/vim-dispatch/)
[2](https://github.com/Shougo/vimproc.vim/)
[3](https://github.com/Shougo/unite.vim)
[4](https://github.com/Shougo/neocomplete.vim)
[5](https://github.com/Shougo/vimshell.vim)
[6](https://github.com/Valloric/YouCompleteMe/)
Pasting the reply I gave in r/vim
Answer to some of the points,
Janus: There are divided opinions in vim community about whether distributions should be used or not. I am on the latter side. But still for just checking out I installed Janus a while ago. Yes it is slow, but it turns out that it is as slow as my then `.vimrc` configuration. I tried to track down the problem. It is because of vim's blocking behaviour during executing external commands. When you write a buffer or switch to a buffer, syntastic, tagbar, powerline statusline, gitgutter, bufexplorer all execute external command. Vim becomes more slow when `.git` repository grow larger or when saving a large file. So how do you solve the problem? Remove those plugins and install Unite.vim[1] with vimproc[2] asynchronous library.
Files that change: If you do external edits more fre
Read the rest
quently then I think it is time to rethink your work-flow. I think there is a common consensus that you should not run live edit in server.
* Indenting pastes* : There is a plugin for that [3] ?
* Opening files inside my project : Last I checked command-t was damn fast, don't know where slowness comes form. Another alternative is `Unite.vim` `file/async` source. It is fast at finding files but goes slow while doing ignore-pattern checking. Without the checking it is DAMN FAST. The `phpcomplete/files` source I created for my php autocomplete plugin[4] easily list 4000+ files in seconds. If you want to list files obeying the patterns in the '.gitignore' or '.hgignore' files. Checkout my unite-file-vcs[4] plugin. It adds a `file/vcs` source that lists files by issuing `git ls-files` or `hg status -c -m -u` command for `git` or `mercurial` projects respectively.
Navigating inside files*: Checkout unite-outline[6]. It shows live output by parsing the current buffer. Unite.vim required. But it does not support css files right now. Adding support should be easy.
So the summary of the story. Move to `unite.vim` and friends ;)
[1] https://github.com/Shougo/unite.vim/
[2] https://github.com/Shougo/vimproc.vim
[3] https://github.com/sickill/vim-pasta
[4] https://github.com/m2mdas/phpcomplete-extended
[5] https://github.com/m2mdas/unite-file-vcs
[6] https://github.com/Shougo/unite-outline
I like unite + vimproc more than CtrlP:
http://www.codeography.com/2013/06/17/replacing-all-the-thin...
https://github.com/Shougo/unite.vim
In Square open-sources its Vim repo, Maximum Awesome