What is the most easy and beautiful way to use asdf on Zorin? using homebew causing some problems
Hi and welcome to the Zorin OS forums!
I'm not familiar with this tool, but based on what I see in the getting started , I'd probably recommend downloading the pre-compiled binary.
Although they do recommend using homebrew, so it might be useful to know which problems are you experiencing.
1 Like
I not so good with linux, but the asdf is the best tool to manage muitiple tools version, its like NVM for nodejs, but for any tool, like python, docker
I switch from MacOS, and when I isntall in Zorin with brew, before restart my PC, the system broke
If you want to discuss the issues with homebrew, I encourage you to open a new thread. I can't make any promises, but maybe is worth a try.
Dependent on whether this is a notebook or desktop keyboard. Up until I retired key elements were sdf, jkl. Why? These are the keys used for inputting Braille into a Braille translation program manually. On a training course we were advised to keep old keyboards as new cheap Chinese keyboards had been programmed differently.
It's not an issue with the keys, the package is really named "asdf". Poor choice of name if I've ever seen one although there's something else called "zxcvbn" so...
1 Like
actually, thre is a reason behind that name, btw, is a good tool
After install de 'asdf' package via homebrew, it worked, i think the problem started after install python trogth asdf.
After a fresh install, I install via the release binaries an it worked, i think that the problem is with homebrew scope, in linux its create a new 'user' on '/home', btw, I will avoid use homebrew on zorin, tks bro
Did you take a look at this pinned issue? It might give you some ideas to work around the issues you're experiencing, in case you prefer to use homebrew.
opened 02:48AM - 21 Aug 20 UTC
closed 03:01AM - 21 Aug 20 UTC
bug
homebrew
<details>
<summary>Background information and why this issue exists</summary>
…
## Background
We regularly see issues raised by Homebrew users where the solution is a missing installation step. I believe this is due to the flow Homebrew users follow which does not include the documentation site:
1. hear about `asdf`
2. install via Homebrew as they do other tools on their system
3. try using `asdf` and it does not work
4. go to GitHub and search/raise an Issue
This is understandable since **few** Homebrew tools require additional steps, though not considered a caveat to installing `asdf` via Homebrew and so we're unable to use the Homebrew post-install hook to direct users to the documentation site - see https://github.com/Homebrew/homebrew-core/pull/54315
Additionally, the `asdf` core team do not want to edit your Shell configurations with a `curl | bash` install script as used in tools like ZSH or nvm. It is a choice, and it comes with pros and cons.
## Solution
Ideally, we would use the aforementioned post-install log from Homebrew to direct users to complete the setup via our Documentation site. Short of this, we must capture users where they end up, GitHub Issues, before they raise an issue and direct them to the documentation site.
---
</details>
After `brew install asdf` [**asdf must be added to your Shell**](https://asdf-vm.com/guide/getting-started.html#_3-add-to-your-shell).
**The documentation [asdf-vm.com](https://asdf-vm.com/guide/getting-started.html) shows all instructions for your OS and Shell combination.**
If we're missing some information or steps let us know and we'll fix ASAP, we want a smooth experience for all!
## Common Homebrew Issues 🍻
These apply to macOS with Homebrew `asdf` installations.
|Issue|Solution|Information|Original Issue/Sources|
|:--|:--|:--|:--|
|`asdf help` or `asdf <command>` does not work with Homebrew installation|✔ Ensure `asdf` is added to shell config|[docs: add to shell](https://asdf-vm.com/guide/getting-started.html#_3-add-to-your-shell)|https://github.com/asdf-vm/asdf/issues/394, https://github.com/asdf-vm/asdf/issues/607|
|`with_shim_executable: command not found ` after `brew upgrade asdf` and macOS BigSur upgrade|✔ Reinstall CLI Tools for XCode Tools and reinstall `asdf`|[Homebrew macOS installation guide](https://docs.brew.sh/Installation#macos-requirements)|https://github.com/asdf-vm/asdf/issues/730#issuecomment-663975814 & https://github.com/Homebrew/brew/issues/7803#issuecomment-648601678|
|`command not found: complete`|✔ Do not use the OMZSH `asdf` plugin with Homebrew installation|OMZSH `asdf` plugin still relies upon the Bash completions. Use the Homebrew installed completions|https://github.com/asdf-vm/asdf/issues/692 discusses `zcompdump` and `compinit` further. Help solving the OMZSH `asdf` plugin issue is welcome, with prior discussion here https://github.com/ohmyzsh/ohmyzsh/pull/8837|
|`brew test <some-tool>` fails with `unknown command: <asdf-installed-tool>. Perhaps you have to reshim`|:warning: Do not rely on `asdf` installed resources for Homebrew tests|Homebrew rewrites `$HOME` during `brew test` which breaks `asdf`. Workarounds reveal a deeper issue of `asdf` dependencies like `sed` not being available in the `brew test` environment. See original issue for more details|https://github.com/asdf-vm/asdf/issues/794|
<!-- Removed items
|`brew upgrade` updated `asdf` which wiped all plugins, shims and installs|✔ set `ASDF_DATA_DIR` before install and before sourcing `asdf.sh`/`asdf.fish`|See [environment variables section in docs](https://asdf-vm.com/#/core-configuration?id=environment-variables)|https://github.com/asdf-vm/asdf/issues/797|
-->
**If you identify a problem not covered here, please open a new Issue to discuss and attempt to resolve before we add it here!**
I'm sure they have a reason but... I can't say that it's a very catchy name What is the reason, by the way? I tried looking for it briefly but didn't find any mentions about the name.