export environment before clone? #132
Answered
by
xenoterracide
xenoterracide
asked this question in
Q&A
-
I've noticed that our corporate proxy is blocking some stuff on github and that they have zi ice lucid wait cloneonly proto"git" nocompile notify \
atclone"install --compare -D colors/desertink.vim $VIM_COLOR/desertink.vim" \
atpull"%atclone"
zi light toupeira/vim-desertink for some reason it's only these # ~/.zshrc
function vim_setup() {
cofproxy on # I connect to the corporate proxy
local VIMDIR="$HOME/.vim"
local VIM_COLOR="$VIMDIR/colors"
local VIM_PACK="$VIMDIR/pack"
local VIM_FTPLUGIN="$VIMDIR/ftplugin"
local VIM_FTDETECT="$VIMDIR/ftdetect"
local VIM_AFTER_SYNTAX="$VIMDIR/after/syntax"
zi ice lucid wait cloneonly proto"git" nocompile notify \
atclone"install --compare -D colors/desertink.vim $VIM_COLOR/desertink.vim" \
atpull"%atclone"
zi light toupeira/vim-desertink
zi ice lucid wait cloneonly proto"git" nocompile \
atclone"install -D after/syntax/zsh.vim $VIM_AFTER_SYNTAX/zsh.vim" \
atpull"%atclone"
zi light z-shell/zinit-vim-syntax
zi ice lucid wait cloneonly proto"git" nocompile \
atclone"install -D syntax/systemd.vim $VIM_AFTER_SYNTAX/systemd.vim; install -D ftplugin/systemd.vim $VIM_FTPLUGIN/systemd.vim; install -D ftdetect/systemd.vim $VIM_FTDETECT/systemd.vim" \
atpull"%atclone"
zi light wgwoods/vim-systemd-syntax
# zi ice lucid wait cloneonly proto"git" nocompile \
# atclone"rsync --mkpath --exclude '.*' --archive . $VIM_PACK/local/start/editorconfig" \
# atpull"%atclone"
# zi load editorconfig/editorconfig-vim
}
vim_setup # ~/.zshenv
if [ -f /usr/local/cof/bin/cofproxy ]; then
source /usr/local/cof/bin/cofproxy > /dev/null 2>&1
cofproxy on
fi this exists outside fo the function and has no issue whatsoever zi wait for \
OMZL::theme-and-appearance.zsh atload"unalias ls" \
OMZP::colored-man-pages \
OMZP::systemd \
OMZP::direnv \
OMZP::gitignore
|
Beta Was this translation helpful? Give feedback.
Answered by
xenoterracide
Feb 23, 2022
Replies: 1 comment 4 replies
-
Fixed it, the problem was actually that I had set |
Beta Was this translation helpful? Give feedback.
4 replies
Answer selected by
xenoterracide
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fixed it, the problem was actually that I had set
proto"git"
which is blocked