Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Shougo
    @Shougo
    autocmd MyAutoCmd ColorScheme hybrid_material set bg=dark
    amikai
    @amikai
    Sorry XD
    Shougo
    @Shougo
    the syntax is wrong
    amikai
    @amikai
    😂
    amikai
    @amikai
    https://github.com/amikai/nvimrc/blob/experiment/dein_plug.vim#L38 This is my setting, i put the echom in L38. If i repoen twice, the echom not work.
    Shougo
    @Shougo
    ?
    You need to source it.
    :source dein_plug.vim
    amikai
    @amikai
    Oh, I know where wrong is.
    thanks
    amikai
    @amikai
    Can i show the loaded plugin in dein?
    Shougo
    @Shougo
    ?
    I don't understand why it is needed.
    You can check it by dein#is_sourced(name).
    amikai
    @amikai
    I want to check my vim config correct or not
    Sometime, my script in on_map and on_source .. is wrong. Because i an not familiar with vimscript
    Tobias Witt
    @ohcibi
    can i execute vim-commands after installing? i tried with 'build': ':UpdateRemotePlugins' but I got an error after installling (would be interesting is UpdateRemotePlugins is even necessary when using dein. The plugin I'm using only has snippets for Plug)
    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.
    Bobby
    @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.
    Bobby
    @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.
    Bobby
    @taigacute
    Not like this, maybe my file loading order is wrong except