You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the dotfiles (.tool-versions file as well as any plugin specific default files - such as .default-gems or .default-npm-packages) all live in the $HOME folder.
Consider moving those to the approved and standardized config location (XDG_CONFIG). Perhaps "$XDG_CONFIG/asdf/" would be an appropriate location with a hard-coded "~/.config/asdf/" as a fallback when XDG_CONFIG is not set. For backward compatibility the tool could futher fall back to the current locations for some time to allow people time to transition.
The text was updated successfully, but these errors were encountered:
This ticket actually seems like a duplicate of #687, with a more specialized use case (XDG_CONFIG instead of any location). Can I close this ticket @brennanfee and continue discussion on #687 ?
@Stratus3D Yes, feel free to close this ticket. 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 nearly all Linux distributions and if implemented with a default when NOT set can work equally well on Mac and Windows.
Currently, the dotfiles (.tool-versions file as well as any plugin specific default files - such as .default-gems or .default-npm-packages) all live in the $HOME folder.
Consider moving those to the approved and standardized config location (XDG_CONFIG). Perhaps "$XDG_CONFIG/asdf/" would be an appropriate location with a hard-coded "~/.config/asdf/" as a fallback when XDG_CONFIG is not set. For backward compatibility the tool could futher fall back to the current locations for some time to allow people time to transition.
The text was updated successfully, but these errors were encountered: