Roland Schaer

The error `mach-o, but wrong architecture` indicates that the `iStats` Ruby gem expects another chip architecture. I assume you're using a new M1 chip? Looks like the `iStats` gem does...

Prepending the `command` with `arch -arm64` in the `index.jsx` seems to resolve the issue but iStats does not work 100%. Fan and battery stats seem to work but others return...

Thanks for that workaround @stevespringett. Unfortunately `istats` does not support M1 (yet) and my C and SMC knowledge are inexistent.

I assume you did use `sudo`? Already tried remove and re-install the gem? ``` ❯ sudo gem uninstall iStats Remove executables: istats in addition to the gem? [Yn] Y Removing...

I assume the [condition](https://github.com/jdx/mise/blob/main/packaging/standalone/install.envsubst#L47) for libc does not match in this case, not setting the `-musl` suffix.

Guess this would be handy for other backends like `cargo` as well (already requested multiple times). Only question is how this could work with `install` and `use` where you can...

@jdx Opened https://github.com/jdx/demand/issues/53 to address this. I guess a new `Dialog` component is the best option to not break backwards compatibility. `Confirm` can be deprecated at some point as `Dialog`...

I toyed around a bit with this idea and tried to come up with an extensible way to define these user inputs. VS Code also has something similar in this...

Yes you might be right about overthinking this. Nevertheless the issues stay the same and `demand` is not able to deal with the multithreading/interweaving nature of the console output in...

This looks inconsistent indeed, will need to dig into this since it works for some and not for others. In the meantime i would have suggested to use the workaround...