Trevor Brown

I know some existing version managers (like rbenv for Ruby) currently look for `.default-gems` in the users home directory. I don't know if rbenv allows the user to customize the...

From @brennanfee on #844: > I would STRONGLY encourage that #687 be updated to refer to and use XDG_CONFIG as its implementation. Given that it has become a standard on...

@jackmac92 can you explain exactly what commands you ran to setup asdf? Those errors seem to indicate something wasn't setup correctly. Regardless of where you put asdf on your system,...

> Everything looks correct with how I'm sourcing . /opt/asdf/asdf.sh in my dotFiles, and the issue persists even if I try to resource that file in an interactive shell. So...

Hey @andrewcrook thanks for opening this issue. To confirm, this is an issue with the core of asdf itself. Plugins don't get to control the version-resolution process. I agree that...

This is a bug we need to fix. In the meantime https://github.com/asdf-vm/asdf/issues/1103#issuecomment-990795248 is a good workaround that shouldn't cause any future issues for you all.

Does my comment here help at all? https://github.com/asdf-vm/asdf/issues/1002#issuecomment-884197641 Given the output of `asdf current` it shouldn't be too hard to find the version file closest to `$(pwd)`.

We've avoided doing this because as you can see it requires aliasing `cd` to some other function in Bash which is 1). something that is frowned upon (for good reason)...

I re-opened this issue so others can more easily find it. I think this would be a good feature if it is optional. A PR is welcome but no hurry.

@augustobmoura you shouldn't be calling `asdf` commands from inside a plugin's callback script, however I understand why you are doing it. symlinking one version directory to another is definitely not...