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
    Q: Cannot load colorscheme when reloading .vimrc.

A: You must write |:colorscheme| lines after |dein#end()|.
>
    call dein#add('tomasr/molokai', {'merged': 0})
    ...

    call dein#end()
    colorscheme molokai
<
Or you can use |dein#source()| for it.
>
    call dein#add('tomasr/molokai', {'merged': 0})
    call dein#source('molokai')
    colorscheme molokai
<
    Please read dein.vim documentation
    Michael Sale
    @mikesale
    should this lazy load be valid?
    call dein#add('zchee/deoplete-zsh', {'on_ft': 'zsh'})
    Shougo
    @Shougo
    yes
    amikai
    @amikai
    I use dein install some colorscheme, and use the Denite colorscheme to switch colorscheme. But i want to change background color when switching colorscheme. I put set bg=light in hook_add and hook_source, and it is not work. How should i do?
    Shougo
    @Shougo
    I don't know. Because I don't use set bg
    Please upload your configuration.
    amikai
    @amikai
    @Shougo , This is my config . https://github.com/amikai/nvimrc/blob/experiment/plugins.toml#L11
    Shougo
    @Shougo
    Hm
    amikai
    @amikai
    I have two colorscheme gruvbox, and vim-hybird-material. I want to set background automatically when switch colorscheme by Denite colorscheme.
    Shougo
    @Shougo
    I have tested your configuration.
    You should use autocmd ColorScheme gruvbox set bg=light instead.
    amikai
    @amikai
    Thanks
    And what's wrong in my original setting
    Shougo
    @Shougo
    g:colors_name is not set correctly in ColorScheme autocmd
    amikai
    @amikai
    mm
    It still has something wrong. In this setting -> https://github.com/amikai/nvimrc/blob/experiment/plugins.toml. First , I use Denite colorscheme to select gruvbox and set bg=light work. Second i use Denite colorscheme select hybrid-material , but set bg=dark not work
    Shougo
    @Shougo
    autocmd MyAutoCmd ColorScheme gruvbox set bg=light
    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
    I source on this file https://github.com/amikai/nvimrc/blob/master/init.vim
    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*