Integrated terminal does not launch when project folder contains special/unicode characters

[VitorLuizC]

• VSCode Version: 1.3.0-insider
• OS Version: Windows 10 Home

Steps to Reproduce:

1. Open a folder with special characters;
2. Try to open the integrated Terminal;

[Tyriar]

@VitorLuizC can you paste in some of the problem characters? Also do you have any terminal-specific settings set in your settings.json?

[VitorLuizC]

My folder's name is "Paçoca", so the "ç" is the only special character, and no I didn't have any terminal-specific settings in my settings.json.

I've tried to open integrated terminal in another folder without special characters("Pacoca") and it worked.

[Tyriar]

Seems fine on stable and insiders on Linux:

Perhaps it's only happening on Windows?

[VitorLuizC]

I don't know if it matters but that folder is inside my OneDrive folder.

---

After a new test i've checked that doesn't matter.

[ZCShou]

Chinese folder or Japanese folder so does on Windows 10！！

[Tyriar]

Must be a windows thing, I'll try have a look at this for v1.3

[hakanostrom]

Can confirm it effects on a new installation of v1.2.1 and on windows.
Folders causing this for me is when opened as "root" and containing swedish letters (åäö). Also if folders above "root" contains special characters.

[Tyriar]

I had a look at this and it appears to be an upstream issue, moving to backlog.

[joseph-iussa]

Can confirm this is happening for me as well (just updated to 1.2.1 and currently on Windows 10). Behaviour is exactly as shown in VitorLuizC's image, except that I have no special characters in my path, and in fact the problem still occurs with no folders or files open and just the initial untitled document displayed.

I recently upgraded to Windows 10 from Windows 7 and the problem was not present while on Windows 7.

[svekl]

For me it happens for russian characters, I have "Сергей" in path on Win 10

[xmichaelx]

Confirm for polish letters in path on Windows 10.

[hs3180]

+1 for Chinese

[Igmat]

+1 for Russian on Windows 10. It doesn't matter are there any special characters in path for opened by VSCode folder. Having them in Windows username will be enough to get integrated-terminal crashing.

[osnoser1]

Not only special chars, i think that are all unicode characters.
My user folder is 'Alfonso Andrés'.
Windows 10.

[Dzienny]

I encountered this problem today. I think I found the culprit. The vscode uses pty.js to open the terminal. https://github.com/Microsoft/vscode/blob/a6c845baf7fed4a186e3b744c5c14c0be53494fe/src/vs/workbench/parts/terminal/electron-browser/terminalProcess.js (line: 30)

And on the pty.js project I found the following open issue: chjj/pty.js#173

[Tyriar]

@Dzienny yes it could be either pty.js or the dated winpty version it uses.

[the-ress]

I've created a pull request with the fix here: chjj/pty.js#176

[Tyriar]

Fixed thanks to @the-ress's pull request! You can try this out in the Insiders build tomorrow or in stable v1.7.

[srcnalt]

I am facing this error on Linux Solus. No special character on file dir. When I try to compile code (alt+enter) F# Interactive console appears for a moment then I get this error message.

[Tyriar]

@srcnalt make sure you're on the latest version, if you still experience the issue please file a new one via Help > Report Issues 😃

[4e1e0603]

I have the same issue: The terminal process command FsiAnyCpu.exe --fsi-server-input-codepage:65001 failed to launch (exit code: 3221225477)

My path to the folder is without any accents or special characters.

• VSCode Version: Code 1.10.2 (8076a19, 2017-03-08T14:02:52.799Z)
• OS Version: Windows_NT ia32 6.1.7601
• Extensions:

Extension	Author	Version
Ionide-fsharp	Ionide	2.23.9

[dfilaretti]

Exact same problem here with Ionide on windows 10. Have tried on windows 7 and it works.
Do not have any accents or special chars.

[devmattrick]

Sorry to bump, but I'm not sure if this is related.

When I run rollup -w I get the "The terminal process terminated with exit code" error, but the error code is 259, strangely. Running it in git bash outside of VSCode works fine, but the integrated terminal crashes without fail.