asdf-gcloud doesn't play nice with asdf-direnv about asdf-gcloud HOT 4 CLOSED

I also encountered this bug. The reason I want to use asdf-direnv is the huge boot performance improvement:

Standard asdf:

$ time node -v
v14.14.0

________________________________________________________
Executed in  487.45 millis    fish           external
   usr time  270.40 millis   82.00 micros  270.32 millis
   sys time  394.76 millis  494.00 micros  394.26 millis

Using asdf-direnv:

$ time node -v
v14.14.0

________________________________________________________
Executed in    9.91 millis    fish           external
   usr time    4.75 millis   97.00 micros    4.65 millis
   sys time    3.70 millis  507.00 micros    3.20 millis

from asdf-gcloud.

Thanks for providing this bug report @svirpridon especially with your investigations. I'll need to see if asdf-direnv provides any env vars or context information for me to detect when it is in use 🤔

Apologies for the really late reply, I didn't get a notification about this issue 🙃 (need to check my notification settings)

from asdf-gcloud.

The solution with ${BASH_SOURCE[0]} should work fine. Even upstream plugins use this approach: https://github.com/asdf-vm/asdf-ruby/blob/master/bin/exec-env

from asdf-gcloud.

@hollow I am open to receiving PRs. I would like to know if that syntax changes the required bash version and how, do you happen to know if it will have an affect on this?

from asdf-gcloud.