Highlight or mark installed versions when running `asdf list all <name>`
- Dominant language
- Go
- Stars
- 25.6k
- Forks
- 941
- Avg merge
- 9h 24m
- Merged PRs (30d)
- 3
Description
### Is your feature request related to a problem? Please describe
When I run `asdf list all ` it is useful for me to compare my installed versions against the list of available versions.
For example, I currently have installed `nodejs` versions `14.18.1` and `16.13.1`. I run `asdf list all nodejs` to see if there is a new minor or patch version bump for one of my installed major versions (i.e. `14.x.x` or `16.x.x`).
I don't always remember exactly what versions I have installed and want an easy way to visually understand that `14.18.2` is now available for me to install and `16.13.1` is still the latest.
### Describe the proposed solution
Something like:
```sh
$ asdf list all nodejs
...
14.18.0
14.18.1 (installed) <-- either differentiate with text or colour highlight it
14.18.2
...
16.13.0
16.13.1 (installed) <-- either differentiate with text or colour highlight it
lts-gallium
...
```
### Describe similar `asdf` features and why they are not sufficient
Running `asdf list ` and then `asdf list all ` is cumbersome.
### Describe other workarounds you've considered
As above, running `asdf list ` and then `asdf list all ` is cumbersome and can mean scrolling back and forth to compare the two lists.
Contributor guide
Research direction
The issue names the `asdf list all ` entry point and compares it with `asdf list `; trace both commands to understand how available and installed versions are obtained. Done means installed versions are visibly marked or highlighted in the combined list, while the existing version output remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100