Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

open in external editor does not handle account names with whitespace

See original GitHub issue

Description

I basically have the same problem as #4246. I switched users and reinstalled github desktop. After that it worked. I noticed that in my old account the user had a non ascii character in the name (ö). So maybe this has something to do with non ascii character paths.

Version

GitHub Desktop:Version 1.4.2

Operating system: Microsoft Windows [Version 10.0.17134.345]

Issue Analytics

State:
Created 5 years ago
Comments:9 (8 by maintainers)

Top GitHub Comments

1reaction

msftrncscommented, Nov 13, 2018

The following comment fixed my issue building desktop: https://github.com/nodejs/nan/issues/763#issuecomment-424853241

1reaction

stevewardcommented, Oct 24, 2018

Thanks again for reporting this @edgale. I tested out a few scenarios and was able to successfully reproduce this.

User account with non-ASCII character – VSCode successfully launches.
User account with non-ASCII character and space in the name – VSCode does not launch.
User account with a space in the name and no non-ASCII characters – VSCode does not launch.

I was also able to reproduce this behavior using Atom. Since this is reproducible I’m going to label it as a bug on Windows.