dot/vim
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Change how we decide whether to do an initial PackUpdate - the previous approach worked fine in Vim, but not in Neovim

Browse source
This commit is contained in:
Danielle McLean 2018-01-12 12:40:47 +11:00
parent 1725d1bc14
commit fc62b18488
Signed by: 00dani
GPG key ID: 5A5D2D1AFF12EEC5
1 changed files with 7 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
config/vim/vimrc
View file

@ -7,14 +7,19 @@ function! s:ensure_dir(dir)
endif endif
endfunction endfunction
" These are really clever - minpac will actually be loaded on the fly only
" when you need to update or clean your packages, rather than all the time.
command! PackUpdate source $XDG_CONFIG_HOME/vim/plugins.vim | call minpac#update() command! PackUpdate source $XDG_CONFIG_HOME/vim/plugins.vim | call minpac#update()
command! PackClean source $XDG_CONFIG_HOME/vim/plugins.vim | call minpac#clean() command! PackClean source $XDG_CONFIG_HOME/vim/plugins.vim | call minpac#clean()
silent! packadd vim-sensible " If the pack directory doesn't exist, we haven't installed any packages yet,
if !exists('g:loaded_sensible') " so let's call PackUpdate.
if !isdirectory($XDG_CACHE_HOME . '/vim/pack')
PackUpdate PackUpdate
endif endif
" Use Inkpot, since it's gorgeous, but with a transparent background instead
" of a solid black one.
augroup transparent_term augroup transparent_term
autocmd! autocmd!
autocmd ColorScheme * highlight Normal ctermbg=NONE autocmd ColorScheme * highlight Normal ctermbg=NONE