Repository: vscode
Issue: nushell doesn't work with debugpy (python debugger)
Labels: bug,debug

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Well. I need Python extension to make it run.

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

# The issue description (system details at the bottom):

Seems like even though it says that nushell is supported now in VSCode in August release ([**here**](https://code.visualstudio.com/updates/v1_93#_terminal) is the announce), it still can't be used as one of Internal Terminals when you try to debug python script. It gets call with a sequence not compatible with nushell syntax like this one.

a) Pixi's environemnt python bad command example:
```
cmd /C "c:\dev\data_processing\.pixi\envs\default\python.exe c:\Users\360ci\.vscode\extensions\ms-python.debugpy-2024.12.0-win32-x64\bundled\libs\debugpy\adapter/../..\debugpy\launcher 54917 -- c:\dev\data_processing\test.py "
```
b) Conda's environment python bad command example:
```
c: && cd c:\dev\sfms && cmd /C "c:\programs\miniconda\envs\data_proc\python.exe c:\Users\360ci\.vscode\extensions\ms-python.debugpy-2024.12.0-win32-x64\bundled\libs\debugpy\adapter/../..\debugpy\launcher 50270 -- c:\dev\sfms\test.py "
```
Screenshot:
![Image](https://github.com/user-attachments/assets/14e504d5-dcb7-4ecc-ad7d-6f6af1c904fb)

It DOES work when you just try to run the script because comparing with debug sequence it doesn't have nushell incompatible command in this case. Because when you try to just run it correctly forms the line. Here is example of the command which works

Conda's good and compatible command when you just run without debugger:
```
C:/programs/miniconda/envs/data_proc/python.exe c:/dev/sfms/test.py
```

@anthonykim1, I saw you latest work on having nushell and julia integrated into VSCode, but I think there is a small chance that I misunderstand how it is expected to work?

The isssue is also discussed here in nushell repo:
https://github.com/nushell/nushell/issues/14022
Here is also one of my comments on this problem with some advices from one of the authors:
https://github.com/nushell/nushell/issues/2775#issuecomment-2412005812

@IanManske point outed [here](https://github.com/nushell/nushell/issues/14022#issuecomment-2403325882
) that the problem in these lines where nushell is not supported:
https://github.com/microsoft/vscode/blob/321e1e5b8a0af43a0ee7549713f606936a1ac9ac/src/vs/workbench/contrib/debug/node/terminals.ts#L81

# Details

- VS Code Version: 1.94.2
- OS Version: Win10: 10.0.19045 Build 19045
- Plugins: Python plugin, but no nushell plugin (is it needed?)

Steps to Reproduce:

1. Install nushell in your system.
2. Go to Settings, to to Terminal > Integrated > Default Profile: Windows, set up "path" to installed nushell
3. Have a small python program like ```print("Hello nu in vscode")```
4. Click on the "Run" arrow, selecting "Python Debugger: Debug Python File"
5. Get error message caused by ill-formed command ```Error:   × Invalid literal``` complaining (see the above the full command it calls) about "\" or "&&" symbols in the string.