Open onnimonni opened 2 years ago
@jthegedus @Stratus3D do either (or both) of you have interest in this? I don't want to implement this if there is no desire for it.
Tackling this would make asdf easier to package for distros. Related to #1343, #666.
Is your feature request related to a problem? Please describe
There's so many multiple ways to enable asdf for different shells.
For example I'm interested in replacing
nodenv
withasdf
in the company I'm now working.In our project readme we have now the following steps:
Which is much cleaner than checking if people are using bash/zsh/fish separately and providing multiple installation steps like we need with asdf.
Describe the proposed solution
Add
init
subcommand to asdf which prints out the paths or commands that can be added for corresponding shell.This is how
nodenv
works:Example output using fish shell
Example output using bash:
Describe similar
asdf
features and why they are not sufficientThe third section in getting started page is sufficient but this would make the adoption little bit smoother.
Describe other workarounds you've considered
Pointing people to asdf getting started page from our documentation.