Shougo/dein.vim

Dark powered Vim/Neovim plugin manager

Shougo

@Shougo

Please use hook_post_update instead.

Francisco Lopes

@oblitum

Hi @Shougo, I'll ask the same question I asked on NeoVim, no need to answer there. Is there a way in dein.vim to have a plugin hook that can differentiate after-install and post-update? In docs there's only mention of post-update hooks, but for one plugin I need to do different things on post-install and post-updates. VIM-PLUG supports this and I'm trying to migrate to dein. VIM-PLUG does it like Plug 'foo/bar', {'do': Function('baz')} where baz can be function! baz(info). The info callback parameter has a:info.status which I can check for 'installed', 'updated' or 'force' for when bang is used on PlugInstall!.

Another problem I'm facing with dein is that my vimrc is working fine with neovim, but when starting vim I'm getting errors as if one of the plugins didn't get fully initialized when a VimEnter autocmd I have on my vimrc runs. It's lightline, and on one VimEnter autocmd in my vimrc I do g:lightline#palette().normal.middle[0][1], but that generate errors of non existing s:lightline script var.

Francisco Lopes

@oblitum

there's no issue when it's neovim, no idea why. I get no issues with vim-plug with same code.

Francisco Lopes

@oblitum

it looks like that even in neovim, my VimEnter is running with lightline not yet fully initialized, but no NeoVim it doesn't cause error messages

Francisco Lopes

@oblitum

s/but no/but in/

Francisco Lopes

@oblitum

it seems dein doesn't automatically expand paths in plugin options, ~, $HOME, etc

if 'path' for plugin doesn't exist, it's not created for the clone....

Shougo

@Shougo

Is there a way in dein.vim to have a plugin hook that can differentiate after-install and post-update?

Dein.vim only has post_update hooks.

Dein.vim does not have post_install hook.

Francisco Lopes

@oblitum

ok, I'm back to plug and check pack alternatives

checking*

sadly I've faced many problems on dein migration

Shougo

@Shougo

@oblitum
it seems dein doesn't automatically expand paths in plugin options, ~, $HOME, etc
if 'path' for plugin doesn't exist, it's not created for the clone....

OK. I have implemented it.

there's no issue when it's neovim, no idea why. I get no issues with vim-plug with same code.

Please upload your configuration. I will check it.

Francisco Lopes

@oblitum

I'm doing a big refactor on my .vimrc. Once I finish, I'll upload it to my dotfiles and then I come back here to ask if a dein version is possible

I'll post the dein version and where it's failing or things I'm missing, but anyway... I'm looking to modernized my setup and if I can find something that's both easy to manage from vimrc as plug and that still use native pkg support, and go for that instead.

Stephan Steinbach

@ssteinbach

What is the difference between a "direct install" and a "install"?

Is that instead of using dein#add()?

Shougo

@Shougo

Please see the documentation.

It is already described.

Stephen

@taigacute

[dein] Target plugins are not found.
[dein] You may have used the wrong plugin name, or all of the plugins are already installed.

hi @Shougo
I split my ini.vim and I got this error.

Does the split init.vim need some order?

Shougo

@Shougo

I think plugins is not registered.

I have not ESP skills. So I don't support it without your vimrcs.

Stephen

@taigacute

It works, can you help me see if my split is reasonable?

Shougo

@Shougo

Hm... If so, I think you have executed call dein#update() or call dein#install() in every startup.

Stephen

@taigacute

Not like this, maybe my file loading order is wrong except

Shougo

@Shougo

You should minimize your vimrc.

I will check it later.

Stephen

@taigacute

Thank you very much for your help, I think my order and splitting are problematic.

Issam Maghni

@concatime

Hi there. Firstly, thank you for this plugin. Is there a way to add a "sub repo"?
Something like this https://github.com/mesonbuild/meson/tree/master/data/syntax-highlighting/vim

Shougo

@Shougo

It is already supported

:h dein-options-rtp

Issam Maghni

@concatime

Awesome, thank you!

Stephen

@taigacute

Hi, how to lazy load nerdtree-syntax-highlight? i set this , but it doesnt work

[[plugins]]
repo = 'ryanoasis/vim-devicons'

[[plugins]]
repo = 'mhinz/vim-startify'
depends = 'vim-devicons'
hook_add ='source ~/.config/nvim/rc/plugins/startify.vim'
hook_source = '''
function! StartifyEntryFormat()
    return 'WebDevIconsGetFileTypeSymbol(absolute_path) ." ". entry_path'
endfunction
'''
[[plugins]]
repo = 'scrooloose/nerdtree'
on_map = [['n','<Plug>']]
hook_add = 'source ~/.config/nvim/rc/plugins/allkey.vim'
hook_source = 'source ~/.config/nvim/rc/plugins/nerdtree.vim'

[[plugins]]
repo = 'tiagofumo/vim-nerdtree-syntax-highlight'
depends =['nerdree','vim-devicons']
hook_add = '''
let g:NERDTreeSyntaxDisableDefaultExtensions = 1
let g:NERDTreeDisableExactMatchHighlight = 1
let g:NERDTreeDisablePatternMatchHighlight = 1
let g:NERDTreeSyntaxEnabledExtensions = ['go', 'python', 'html', 'css', 'jsx', 'js', 'vim']
'''

Shougo

@Shougo

@PendragonSaber You should use on_source for vim-nerdtree-syntax.

Your configuration is not lazy.

Note I don't understand what is doesn't work.

We have not ESP skills

Stephen

@taigacute

hmm it means i dont get any colors in nerdtree

Shougo

@Shougo

I don't work for non minimal vimrc report.

Jonathan Lau

@laujonat

Hm, I wasn't having a highlight problem ith my vim configuration with nerdtree before I removed it.

I use dein as a my package manager, and have FZF which come with proconfigured color synax, but replacing wherever you your colors directory is installed with https://github.com/flazz/vim-colorschemes/tree/master/colors, it solved a few problems with highlight syntax.

You can check out the repo. I have a few symlinks that need to be cleaned, but for my current use case, this is working fine https://github.com/laujonat/dotfiles/blob/master/vim/.vimrc

Where communities thrive

People

Repo info

Activity