Backslashes are treated as escape characters

[kabeep]

Environment

• Git Bash version: 5.2.15
• Operating System: Windows 11
• Broot version: 1.53.0

What happened

~/.bashrc :

source C:\Users\me\...\bash\br
treated as
source C:Usersme...bashbr

~\...\dystroy\broot\config\launcher\bash :

cd C:\Users\me\...\directory
treated as
cd C:Usersme...directory

Fix that works for me

function br {
    local cmd cmd_file code
    cmd_file=$(mktemp)
    if broot --outcmd "$cmd_file" "$@"; then
        cmd=$(sed 's/\\/\\\\/g' "$cmd_file")      # Only Changed here
        command rm -f "$cmd_file"
        eval "$cmd"
    else
        code=$?
        command rm -f "$cmd_file"
        return "$code"
    fi
}

[Canop]

I'd like somebody else on Windows to check this.

[Cyrus580529]

Confirmed on Windows 11 / Git Bash.

It's path_to_string in execution_builder.rs — it only quotes paths with whitespace or a quote, so C:\Users\me\dir reaches the outcmd file unquoted and eval eats the backslashes.

Adding \ to that character class quotes it, and eval keeps it intact:

before:  cd C:\Users\me\Roaming
after:   cd 'C:\Users\me\Roaming'

Same thing happens on Unix for a file named a\b. One-line change, I can open a PR.

[Canop]

So, is anybody building a PR from the working fix ?