WIn11 WSL2 escaping characters in Path names

[mhekel]

I wrote this on another issue I didn't realize was closed. sorry

paths with spaces issue

in my .bashrc I have

export NWN_ROOT="/mnt/c/Program Files (x86)/GOG Galaxy/Games/nwnee":$NWN_ROOT
(I've done this with /mnt/c/'Program Files (x86)'/'GOG Galaxy'/Games/nwnee:$NWN_ROOT and ="/mnt/c/Program Files (x86)/GOG Galaxy/Games/nwnee":$NWN_ROOT as well
and every time i get
-bash: /mnt/c/Program: No such file or directory or such. always broken after Program. I even tried using double quotes around each folder and it didn't like the (x86) and so on

I've used wslpath to see how it;s convereted from Windows to WSL. It shows the spaces yet we all know that the spaces break the path..

THe error seems specific to the (x86) syntax error unexpected token ( So I thought I'd do it as 'Program Files (x86)'/ or /Program \Files \(x86\)/Gog \Galaxy/ etc.. what the actual poop?

oh i do have in wsl.conf
```
[interop]
enabled = false
appendWindowsPath = false

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• How to handle cases when windows file path has empty space and needs to be invoked on WSL linux side? (#2807), similarity score: 0.73
• Colon Used as Spaces in Linux PATH (#10399), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[mhekel]

I checked those issues. all seemed to reference if the path was c:/users

[mhekel]

/question

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• How to handle cases when windows file path has empty space and needs to be invoked on WSL linux side? (#2807), similarity score: 0.73
• Colon Used as Spaces in Linux PATH (#10399), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'

[mhekel]

hi, so those other 2 posts I already viewed and they are not helpful at all. Its a really simple question I have about how to escape spaces in paths