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
Originally posted by kenbankspeng February 17, 2025
go 1.24.0 introduced 'go tools' for version management of tools (written in go) required for the project, which many in the community feel is going in the wrong direction.
So I think to myself, well I should just use Mise. But then I hesistated as I currently use Mise as a package manager of bigger things, like rtes and package managers and didn't want to intermingle a multitude of smaller binaries.
Unless my thinking is misaligned, I would be more inclined to use Mise for more things if it supported a simple grouping by the backend used, so that for example, mise list --grouped would list them grouped by the backend they were installed from, and mise list --backend go would list only the tools installed via the go backend.
Thoughts?
The text was updated successfully, but these errors were encountered:
@jdx - thanks for an amazing tool, I have been using it more and more to replace existing tools, hoping to replace my dependence on homebrew in the future.
Would it be possible to define the grouping in the config file as well using nested tables something like the below
[tools]
go = "1.24"
[tools.go]
"github.com/jesseduffield/lazygit" = "v0.48.0"
Discussed in #4436
Originally posted by kenbankspeng February 17, 2025
go 1.24.0 introduced 'go tools' for version management of tools (written in go) required for the project, which many in the community feel is going in the wrong direction.
So I think to myself, well I should just use Mise. But then I hesistated as I currently use Mise as a package manager of bigger things, like rtes and package managers and didn't want to intermingle a multitude of smaller binaries.
Unless my thinking is misaligned, I would be more inclined to use Mise for more things if it supported a simple grouping by the backend used, so that for example,
mise list --grouped
would list them grouped by the backend they were installed from, andmise list --backend go
would list only the tools installed via the go backend.Thoughts?
The text was updated successfully, but these errors were encountered: