generate completions

[BoostCookie]

EDIT:
This is done now. It solves #151. It works the same way as it does in rustup. https://rust-lang.github.io/rustup/installation/index.html

OLD MESSAGE:

This is some starting effort that can eventually solve #151.
I don't know how the build files are being packaged for the different distributions and operating systems. I'm asking for feedback in this regard.

What happens now:
Every time the package is build the completions for the different shells are generated and put into the build directory target/release/build/juliaup-<somehexstring>/out/.

What is left to do:
Add the completions to the packages so that they are available after installing juliaup.

[davidanthoff]

I'm not really familiar with how completion files work. Do we need to drop them into a specific location on user systems? Or do they need to be run? Or something else?

[BoostCookie]

I'm not really familiar with how completion files work. Do we need to drop them into a specific location on user systems? Or do they need to be run? Or something else?

Packages usually install their zsh completions to /usr/share/zsh/site-functions/. If you are an admin that installs stuff manually you should use /usr/local/ instead of /usr/ of course.
Similarly bash completions go into /usr/share/bash-completion/completions/.

So OS repositories (Arch User Repository, openSUSE Tumbleweed, Solus) should definitely package the completions into these directories.

For the "recommended" install method

curl -fsSL https://install.julialang.org | sh

we are only the local user. We could put the completions somewhere in $JULIA_DEPOT_PATH and then do something similar like here

juliaup/src/operations.rs

Line 790 in a9d6755

pub fn add_binfolder_to_path_in_shell_scripts(bin_path: &Path) -> Result<()> {

where we add the juliaup binary directory to $PATH. => We can add our completions directory to the specific shell completions.

Though personally I'm not a fan of fishing around in people's config files. I think we should do it the way rustup does it.
https://rust-lang.github.io/rustup/installation/index.html
With a command

$ juliaup completions bash > ~/.local/share/bash-completion/completions/juliaup

for bash, for example.

[BoostCookie]

I have now followed the rustup way, and added a command that generates the completions.

[fingolfin]

Awesome. Looks good to me, and is quite useful!

[fingolfin]

@BoostCookie unfortunately it seems this now as conflicts that must be resolved?

[BoostCookie]

Is there even any interest in this pull request?
@davidanthoff

[StefanKarpinski]

Yes, this is great functionality. @davidanthoff is quite busy, but please don't be discouraged. We'll get this merged.

[davidanthoff]

We had more changes to the clap structures on main, and I'm a bit worried that those changes might get lost in the simultaneous move of the code to a new file in this PR. So, I just created a new PR off main that just moves the clap structs to a new file, like in this PR. I'm going to merge that right away, and then we can be entirely sure that we don't lose anything in the merge story.

@BoostCookie could you rebase this PR on top of main once I've merged #787?

Awesome PR, thanks!