Use generic_string for path on Windows unix shells

[AntoinePrv]

Fix #2683

[jonashaag]

Can we add a test for this?

[AntoinePrv]

Hmm, bash should already be tested on Windows so it is weird that we had a bug to start with...
Unless there are options to allow Windows paths on Windows bash?

[pavelzw]

I tested it on cygwin:

~/Documents $ ./micromamba.exe shell hook --shell=bash | grep "__mamba_exe()" -A 5
__mamba_exe() (
    "C:\Users\pavel\Documents\micromamba.exe" "${@}"
)

__mamba_hashr() {
    if [ -n "${ZSH_VERSION:+x}" ]; then

Unfortunately, it still uses the windows paths. (got the executable from this commit 0xbe7a@32846b1)

[AntoinePrv]

I'm confused. @pavelzw can you try the last commit? The standard clearly states that the separator should be a /. Or am I not modifying the right function?

[pavelzw]

Just tried it with a brand-new windows server instance with cygwin installed. There, it still uses the windows paths.

admin@windows-server /cygdrive/c/Users/admin/Downloads
$ ./micromamba shell hook -s bash

# Copyright (C) 2012 Anaconda, Inc
# SPDX-License-Identifier: BSD-3-Clause

__mamba_exe() (
    "C:\Users\admin\Downloads\micromamba.exe" "${@}"
)
...

I used the executable from 73b0f54 (#2685).

[Klaim]

I'm approving this but worry that the paths displayed might be misleading to users. Maybe displaying both on windows would be best?

[AntoinePrv]

@Klaim there is no displaying in this PR. This are activation scripts being run when using micromamba activate (the ones that set env variables).

[Klaim]

Ok I thought these paths were also displayed when doing micromamba activate but anyway thanks for clarifying.

[AntoinePrv]

Let's give it a try