diff --git a/knowledge base/asdf.md b/knowledge base/asdf.md index c3f3e99..520dcf8 100644 --- a/knowledge base/asdf.md +++ b/knowledge base/asdf.md @@ -1,8 +1,7 @@ # ASDF -CLI tool to manage multiple language runtime versions on a per-project basis. It works like `gvm`, `nvm`, `rbenv` and `pyenv` (and more) all in one. - -## Table of contents +CLI tool to manage multiple language runtime versions on a per-project basis. It works like `gvm`, `nvm`, `rbenv`, +`pyenv` and others, all in one. 1. [TL;DR](#tldr) 1. [Installation](#installation) @@ -135,9 +134,11 @@ python system 3.11.0 3.10.9 3.9.7 The versions listed in such file can be: - an actual version, like `3.10.9`; plugins that support downloading binaries, will download that versions' binaries -- a git reference, like `ref:v1.0.2-a` or `ref:39cb398vb39`; plugins will download the given tag/commit/branch from github and compile the executable file +- a git reference, like `ref:v1.0.2-a` or `ref:39cb398vb39`; plugins will download the given tag/commit/branch from + github and compile the executable file - a path, like `path:~/src/elixir`; plugins will reference this path to a (custom, compiled) version of the executable -- the `system` keyword; this causes asdf to passthrough to the version of the tool present on the host system and avoid those which are managed by asdf +- the `system` keyword; this causes asdf to passthrough to the version of the tool present on the host system and avoid + those which are managed by asdf ## Further readings @@ -147,13 +148,14 @@ The versions listed in such file can be: - [`.tool-versions` example][.tool-versions example] + +[.tool-versions example]: ../examples/dotfiles/.tool-versions + [github]: https://github.com/asdf-vm/asdf [homepage]: https://asdf-vm.com/ [plugins list]: https://github.com/asdf-vm/asdf-plugins - - -[.tool-versions example]: ../examples/dotfiles/.tool-versions