-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dein support #9
Comments
Hi, On Fri, Apr 22, 2016, 04:18 Khalid H. Ahmed notifications@github.com
Sent from Gmail Mobile. |
As I understand it, dein.vim is a manager for neovim. I am under the impression that neovim has a very different plugin system. I am not sure how the script will work out. Presumably, it is possible as long as we can get an output similar to |
Actually, neovim and vim have the same plugin system. Most people use the same vimrc for both of them :) The real problem is how dein (the plugin manager), manages plugins. It seems to cache them such that, there is no need to populate run-time path on each startup. Here is the profile you asked for: nvim_profile_with_dein.txt And I know, I have lots of plugins :) |
Thank you so much for sharing the files. From what I can see from the files you sent me, it seems that Can you please tell me the output of the following two lines (BASH) echo $HOME
vim -c ':exec ":silent !echo ".&rtp | exec ":q!"' # might be nvim |
dein copies the files to a folder named ".dein" (or any name you choose). And in that directory it creates the autoload, plugin, and other directories, which vim wants. However, in case of vim-plug and other plugin managers, they don't have such a folder with all files from different sources merged. Instead of this, they know which plugins are added and perform runtime path population during startup. Consider these two:In case of vim-plug, note how vimproc and vinegar are located in their corresponding directories namely, vimproc.vim and vim-vinegar. With vim-plug3224.315 000.200 000.200: sourcing /Volumes/Home/.config/nvim/plugged/vimproc.vim/plugin/vimproc.vim However, in case of dein, vimproc and vinegar with other plugins are located in the same directory (Path). With dein1438.170 000.177 000.177: sourcing /Volumes/Home/.config/nvim/dein/.dein/plugin/vimproc.vim |
Oh, now I see your point. I was looking at the following block:
So, @Shougo, I would love to provide support for |
Yeah, I know that some plugins tend to use the same name. I think I have already seen an issue on dein's github page for that. However, it's very rare :) I could be wrong, but in the issue I mentioned there was only one conflict reported. Sorry, I don't remember the issue title, else I would have pointed you to it. The cached folder is where cached files are saved. However, there is also another directory named "repos", where all plugin's repos are stored (it's just like vim-plug's plugged directory). Somehow the two can be used together to detect which file belongs where. |
Here is the directory structure for dein generated, using Update: |
Hm. This is for merged plugins? |
Opps missed this one :)
The following is the &rtp output: I deleted this bit from the above output, as it makes things confusing. It may be a leftover from vim-plug or a local repo (not sure): |
I use Dein with Vim, not NeoVim. I was able to get it working by grepping |
Any progress on this? |
I'm willing to merge any pull request to support this. If someone can share a typical vim config that relies on |
Hi @hyiltiz,
This is a very useful tool. I use it a lot, since I have lots of plugins :(
Lately I wanted to try dein.vim. However, I could not profile it using your tool. I was wondering if you can support dein.vim too? The problem is dein.vim caches its files very differently from other plugin managers.
Thanks.
The text was updated successfully, but these errors were encountered: