After the v2 merge, I always get this error on startup:
[zplug] WARNING: ZPLUG_SHALLOW is deprecated. Please use 'export ZPLUG_CLONE_DEPTH=1' instead.
I can reproduce this with the following minimal .zhsrc:
source ~/.zplug/init.zsh
zplug "b4b4r07/zplug"
zplug check || zplug install
zplug load --verbose
I have removed the cache and the completion file, and this is a fresh zplug install (e.g. I nuked the previous ~/.zplug)
tachikoma% uname -a
Linux tachikoma 4.2.0-35-generic #40-Ubuntu SMP Tue Mar 15 22:15:45 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
tachikoma% zsh --version
zsh 5.1.1 (x86_64-ubuntu-linux-gnu)
I also have to say that I wasn't expecting to upgrade to v2, I just wanted to update my packages - maybe the upgrade can be made opt-in?
Thanks!
@asymmetric Hi,
We actually recommend you to upgrade to v2 but if you don't want to do so you can just use v1:
zplug "b4b4r07/zplug", at:v1
Hi b4b4r07, the actual problem (having [zplug] WARNING: ZPLUG_SHALLOW is deprecated. Please use 'export ZPLUG_CLONE_DEPTH=1' instead. on every shell) hasn't been fixed though - why was the issue closed?
Did you want to update v2 or not? I closed because I thought you wanted to use v1.
Yes, I am running v2, and the problem is only happening since I upgraded.
As the error suggests, you cannot use ZPLUG_SHALLOW because it's deprecated. Please run unset ZPLUG_SHALLOW.
The thing is I don't set it myself anywhere, as far as I know. As I said, it's a fresh zplug v2 install.
Any ideas where I could look for it?
I'm not sure but I think it doesn't matter if it's fresh zplug or not because the ZPLUG_SHALLOW is exported to other processes.
OK, a reboot has fixed it, so this seems to be a transient problem for people upgrading from to v1 to v2. It was for me anyway.
I'm glad that it's fixed. Tell us anytime if something happened.
Do you think it would make sense to have a unset ZPLUG_SHALLOW in http://git.io/zplug?
As you mentioned earlier, it is just a transient issue. I believe restarting the shell (or tmux if you're using it) would fix the problem, so I don't think it's necessary.
Most helpful comment
OK, a reboot has fixed it, so this seems to be a transient problem for people upgrading from to v1 to v2. It was for me anyway.