Gábor Csárdi

Actually, I like this as it is. It would be weird to update aliases from `system make-links`, if no new version is installed. Instead we could have a `rig system...

Implementation in #151

I just added this in #151: ``` ❯ ./target/debug/rig available name version release date type ------------------------------------------ 4.1.3 4.1.3 2022-03-10 release 4.2.3 4.2.3 2023-03-15 release 4.3.0 4.3.0 2023-04-21 release next 4.3.0...

Now released in rig 0.6.0.

It works fine, even in the same shell.

I'll close this for now, as R is probably coming soon to arm64 Windows.

To clarify. * We could relatively easily implement the use case where admin installs various R versions, and each user can set their own default. * It is much harder...

~~Seems like Rstudio behaves differently in different OSes:~~ Correction: - RStudio >= 2023.06.0 works well on all OSes. - RStudio

There is now https://crates.io/crates/clap_mangen which is not bad, although it is somewhat cumbersome because we need to iterate over the subcommands and create a separate manual page for each.

Yes, I agree that it would have been better the other way, but can we really change it at this point? It will break a lot of things, no?