Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mise support for grouping #4442

Open
jdx opened this issue Feb 18, 2025 · 2 comments
Open

Mise support for grouping #4442

jdx opened this issue Feb 18, 2025 · 2 comments

Comments

@jdx
Copy link
Owner

jdx commented Feb 18, 2025

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, and mise list --backend go would list only the tools installed via the go backend.

Thoughts?

@jdx
Copy link
Owner Author

jdx commented Feb 18, 2025

in addition to this I think there should be a mise ls --backend ubi filter we don't currently have

@benpops89
Copy link

@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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants