nushell 0.94.1 breaks Windows path handling

[CarterLi]

Describe the bug

Error:   × Invalid literal
     ╭─[C:\Users\zhang\AppData\Roaming\nushell\config.nu:792:17]
 791 │ #use ~/.starship.nu
 792 │ alias curl = c:\msys64\clangarm64\bin\curl.exe
     ·                 ───────────────┬──────────────
     ·                                ╰── unrecognized escape after '\' in string
 793 │ alias vim = nvim
     ╰────

How to reproduce

Windows style paths in config file result in error unrecognized escape after '\' in string

Expected behavior

Don't error

Screenshots

N/A

Configuration

N/A

Additional context

Regression in 0.94.1. It worked in 0.94.0

[YizhePKU]

@devyn Probably a side-effect of #13001.

[Deebster]

You can replace each backslash with a double backslash, but it's very tedious to do this outside of scripts.

I've downgraded until it's fixed with cargo install --version 0.94.0 nu (edit: hmm, I'm now seeing the issue on 0.94.0)

[CarterLi]

starship generates nu scripts with Windows style paths.

BTW starship works weird after upgrading nu to 0.94.0+

[chtenb]

Huh, I downgraded to 0.94.0 again, but the issue persists, as in, my config scripts that worked earlier on 0.94.0 no longer work after downgrading from 0.94.1!

[kubouch]

On my Windows end, the issue appears at 0.94.1. The version 0.94.0 works fine.

[rogtino]

Hello team,would you mind posting a bug fix release?

[kubouch]

Yes, it's coming within a day.