Windows 10 - Bash (Ubuntu) | How to run Atom build with bash command?

[thenets]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

I got a lot of problems when I try to run commands on Atom to "bash.exe". No matter what extension I use.

Steps to Reproduce

1. Enable "Bash Ubuntu" for Windows 10.
2. Setup compiler for my application on "Bash Ubuntu".
3. Test from "bash.exe" and "powershell.exe". Everything work ok.
4. Install Atom.
5. Create an runner on Atom.
6. Get msg "Erro: 0x80070057"

Expected behavior: Expected the same result as Powershell:

Actual behavior: But I got this error:

Reproduces how often: always happen.

Versions

Atom : 1.15.0-beta0
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0

apm 1.15.3
npm 3.10.5
node 4.4.5 x64
python
git 2.9.0.windows.
visual studio 2015

Windows 10 Pro (with all lastest updates)

Additional Information

I got the same problem with any extension I use.

I wrote an question at Stack Overflow too:
http://stackoverflow.com/questions/42121927/windows-10-bash-ubuntu-how-to-run-atom-build-on-bash

I found two things can help

• Disable Legacy Mode on Powershell (Error: 0x80070057 microsoft/WSL#7)
• Use Powershell ISE (Error: 0x80070057 in ISE microsoft/WSL#430)

[damieng]

We support building Atom on Windows using our native Windows environment only.

There is no support and no plans to support compiling the Linux version of Atom on Windows using WSL.

[thenets]

:/ ah, ok. Thanks, anyway.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!