Improve micromamba transaction message

[ruben-arts]

Before:

Transaction finished

To activate this environment, use:

    $ [micro]mamba activate <environment>

Or to execute a single command in this environment, use:

    $ [micro]mamba run -n <environment> mycommand

Examples of the result now:

$ time ./build/micromamba/micromamba create -c conda-forge --yes -n test python

# results in

Transaction finished

To activate this environment, use:

    micromamba activate test

Or to execute a single command in this environment, use:

    micromamba run -n test mycommand
    

$ time ./micromamba create -c conda-forge --yes -p ~/testing python

# results in, note the -p or -n

Transaction finished

To activate this environment, use:

   micromamba activate /home/rarts/testing

Or to execute a single command in this environment, use:

    micromamba run -p /home/rarts/testing mycommand

Notable improvements:

• If is_micromamba is true micromamba will be used as the executable
• Use no $ to make the line double click + copy + paste.
• Use -p when using prefix, use -n for a named env.

[AntoinePrv]

Could this be a method of the command?

[ruben-arts]

This will not be needed anymore.

[AntoinePrv]

Nice, thanks!

[wolfv]

Unfortunately the executable won't work for activate because the activation is actually implemented on the shell level. So it has to be micromamba activate ....

[AntoinePrv]

So maybe you can switch with ctx.is_micromamba?

[ruben-arts]

Unfortunately the executable won't work for activate because the activation is actually implemented on the shell level. So it has to be micromamba activate ....

Should we keep the run with the executable or keep the also move that to micromamba?

[wolfv]

I think the executable path can be long and weird so maybe just micromamba is better

[ruben-arts]

@wolfv @AntoinePrv I updated the PR, pretty sad that the executable thingy didn't work... But it should work in normal situations now!

[Hind-M]

Thanks!