Trevor Brown

Closing as I believe this has been fixed by the Go rewrite.

Sorry for the late reply here @DerekTBrown. I don't think we have a perfect solution for you. There are a couple things I think could work: ## 1. Symlink `.tool-versions`...

Closing as this is not an issue with asdf-ruby.

Closing this issue because, ironically, asdf was rewritten in Go, and the `asdf global` command has been replaced with `asdf set`.

I'm going to close this as this isn't an issue with the code in this repository.

Do not merge this until the GitHub action has been updated to default to 0.15.0. The action currently relies on the Bash code on the master branch, and once this...

This can be merged after https://github.com/asdf-vm/actions/pull/578 is released.

I am getting the same error on asdf 0.16.7: ```bash $ asdf cmd nodejs nodebuild --version error running extension command: Plugin named nodejs does not have a extension command named...

Manually downloading kerl as you are doing should not be necessary. Can you explain why you are doing that? Also, overriding `$HOME` as you are doing and not setting `$ASDF_DIR`...

Moved to the elixir plugin as this doesn't seem to an issue with asdf core.