Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Tobias Witt
    @ohcibi
    note to self: if you symlink ~/.vim to ~/.config/nvim instead of the vimrc file directly dont forget to do it on your new computer as well
    Michael Yang (xdazz)
    @kiooss

    @Shougo
    In dein's readme, the example config is like below.

    call dein#add({path to dein.vim directory})
    call dein#add('Shougo/deoplete.nvim')

    Can here be just call dein#add('Shougo/dein.vim')

    Shougo
    @Shougo
    You can write like it.
    But it adds the dein.vim path to Vim runtimepath.
    You have added the path to runtimepath in your vimrc.
    So it will be duplicated path.
    Michael Yang (xdazz)
    @kiooss
    Got it, thanks. @Shougo
    Tobias Witt
    @ohcibi
    @Shougo i'm curious. can you elaborate why one needs to explicitly tell dein to manage dein?
    Shougo
    @Shougo
    It is hard to tell
    You should know dein#add(local path) and dein#add(repository path) difference.
    You have installed dein.vim manually.
    So it should be dein#add(local path)
    Tobias Witt
    @ohcibi
    @Shougo in fact I don't know about the difference but I'm already blindly respecting that. But that wasn't my question. The question was, why do i need to tell dein at all that it should manage dein? (no matter if installed locally or per repository?) Is it to benefit from the caching for dein as well? Would dein work without telling dein to manage dein but then dein wouldn't be cached?
    Shougo
    @Shougo
    Hm.
    Of course, you don't have to manage dein.vim.
    Because it is already installed
    If you manage dein.vim, you can update dein.vim by dein.vim.
    It is not special feature.
    But it is useful and vim-plug doesn't support.
    Maik Klein
    @MaikKlein
    Any idea why I can't access the help file with :h dein?
    Shougo
    @Shougo
    call dein#recache_runtimepath()
    I think tag file is broken
    Wang Shidong
    @wsdjeg
    will dein support vim7.4.1689 in the feature?
    in Ubuntu 16.04, the vim is 7.4.1689
    Shougo
    @Shougo
    No.
    Please use ver.1.5 if you want to Ubuntu 16.04
    Because I have dropped Vim 7.4 support intentionally
    Wang Shidong
    @wsdjeg
    Ok, thanks
    Does it support 7.4.0052
    Stokhos
    @stokhos
    hi Shougo, I installed gruvbox through dein,
    however neovim keep telling me Cannot find color scheme 'gruvbox'
    set runtimepath+=/home/stokhos/.dein/repos/github.com/Shougo/dein.vim
    Stokhos
    @stokhos
    nvm I figured it out
    Shougo
    @Shougo
    You need to execute coloscheme gruvbox after dein#end()
    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
    @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