fb76955440
chore: update electron@27.2.1 ( #202053 )
...
* chore: bump electron@27.2.1
* chore: enable code cache support for custom standard schemes
Refs 267cbc841ef842ead6bc
2024-01-09 08:33:34 +01:00
d9f91002d4
wsl code: pass SERVERDATAFOLDER
2022-01-24 14:43:43 +01:00
e08e4d3fe1
Move `--ms-enable-electron-run-as-node` to a later location ( #136786 )
...
* Move `--ms-enable-electron-run-as-node` to a later location, which is not fatal in Electron builds that don't know it
* undo bad change
2021-11-09 15:11:12 -08:00
ac29daaf3b
Fixes #136771 : update to Electron v13.5.2 and pass `--ms-enable-run-as-node` together with `ELECTRON_RUN_AS_NODE`
2021-11-09 19:09:26 +01:00
59df6b40f1
code.sh: Prevent stealing of stdin (for #99815 )
2020-10-16 22:45:38 +02:00
e8760a5d6c
Fix capitalization of GitHub org
2020-09-17 11:43:03 +02:00
b5d8e6e72c
code.sh: add quotes to `export WSLENV`
2020-08-14 13:56:34 +02:00
aa46585224
code.se: Improve version check for WSL2
2020-06-22 21:49:24 +02:00
c93c29c357
code.sh: loosen check for WSL2
2020-06-19 23:42:58 +02:00
29b5f87288
code.sh: debug with VSCODE_WSL_DEBUG_INFO
2020-06-03 21:51:04 +02:00
4eadd58d11
Unable to launch vscode in remote mode from WSL2 (custom kernel) Fixes https://github.com/microsoft/vscode-remote-release/issues/2809
2020-06-03 21:43:18 +02:00
798e32cb83
code.sh: pipe error still printed. For https://github.com/microsoft/vscode-remote-release/issues/1420
2019-09-19 16:15:13 +02:00
945d678d36
uv_pipe_open error when starting code-insiders from WSL microsoft/vscode-remote-release#1420
2019-09-17 18:06:55 +02:00
68c1123b33
Code-insiders started from WSL doesn't return to console/ doesn't connect Fixes microsoft/vscode-remote-release#1369
2019-09-06 10:46:53 +02:00
587c673c7f
wsl2 workaround no longer necessary
2019-09-03 17:51:53 +02:00
df880b0434
Workaround for broken WSL2 in Win build 18947. For #77898
2019-08-23 15:36:14 +02:00
49b51b32b2
Run wslCode with electron (fixes vscode-remote-release#914)
2019-07-30 11:41:14 +02:00
e40623fcb7
Revert "Failure to launch VSCode from WSL2. Fixes microsoft/vscode-remote-release#914"
...
This reverts commit 0288def891
2019-07-23 09:17:05 +02:00
0f90403c57
windows/code.sh: convert to sh
2019-07-16 17:05:57 +02:00
0288def891
Failure to launch VSCode from WSL2. Fixes microsoft/vscode-remote-release#914
2019-07-16 12:21:46 +02:00
99ebdaa7dc
Code-insiders started from WSL doesn't return to console/ doesn't connect. Fixes microsoft/vscode-remote-release#780
2019-06-24 18:10:47 +02:00
769e5d2ad2
win code.sh fix
2019-06-20 16:50:29 +02:00
3bffb1561c
code doesn't open in remote-wsl under WSL2. For microsoft/vscode-remote-release#714
2019-06-19 11:44:02 +02:00
ecf9a9f764
code.sh: add datafolder
2019-05-29 23:18:50 +02:00
b331ec3386
code.sh for wsl: avoid cmd.
...
Fixes microsoft/vscode-remote-release#42
Fixes microsoft/vscode-remote-release#170
2019-05-23 12:46:09 +02:00
4237ce04c5
change publisher
2019-04-30 23:34:46 +00:00
e44a5ce145
Resolved regression in WSL launch script
2019-04-24 07:40:11 +08:00
87fd1d4534
Strange console output when using WSL
2019-04-23 16:05:39 +02:00
12cb89c82e
Make sure Windows bash CLI works with spaces in user name
2019-04-19 09:46:57 -07:00
e146527fec
win/code.sh: falback when wslpath not present
2019-04-16 10:44:44 +02:00
84b1474d09
Code Insiders latest update break the `code-insiders` commands inisde WSL. Fixes #72260
2019-04-15 16:11:31 +02:00
f999a29671
add quality to win/code.sh
2019-04-12 14:58:29 +02:00
b7ec5e8e6c
Use wsl ext
2019-04-11 09:58:18 +02:00
9588b6fe87
Launching "code" from git bash fails with "cannot find module" error. Fixes #58950
2018-10-03 10:22:37 +02:00
8505dcc469
enable CLI when invoked from WSL on modern (RS4) hosts
...
Fixes issue #39892
There's one minor gotchya: this script tests for a modern WSL release
(which supports the WSLENV feature) using the existence of
/bin/wslpath. Per https://docs.microsoft.com/en-us/windows/wsl/release-notes ,
wslpath was added in build 17046 but WSLENV is only supported in
the subsequent build (17063). Both those builds were only shipped as
Windows insider builds, so this test should be safe enough.
2018-03-02 11:17:03 -08:00
9c298b0978
Fix cli.js always opening from WSL shell
...
Also support relative paths
Fixes #13138
2017-01-13 18:01:35 -08:00
97bef4bdc6
Update to electron 1.4.x ( #15298 )
...
* electron 1.4.6
* fix broken DND image feedback
* OSS input
* remove cat.exe as it is no longer needed
* update electron.d.ts
* set new ELECTRON_NO_ASAR environment for forked processes
* Automatically enable high contrast theme when enabled in Windows (fixes #15360 )
2016-11-14 14:27:53 +01:00
6fa85223ef
Electron Update 1.x ( #11157 )
...
* use electron 1.3.4
* ATOM_SHELL_INTERNAL_RUN_AS_NODE => ELECTRON_RUN_AS_NODE
* OSS input
* update electron.d.ts
* workaround for #8708
* bump oniguruma and chokidar with custom fsevents
* build with appveyor config from master
* oops, still use ELECTRON_RUN_AS_NODE
* use electron 1.3.5
* optional fsevents
* add cat.exe to workaround output issues
* use cat for tests
* remove some now obsolete ELECTRON_NO_ATTACH_CONSOLE
* also pipe output to cat for code.sh on windows
* unset ELECTRON_RUN_AS_NODE for appveyor
* fix tfs builds?
* fix build
* fix build?
* use cat only when running tests locally
2016-09-14 07:29:20 +02:00
79c02d4dba
Fixed `code.sh` to start VS Code under Cygwin.
2016-08-13 20:31:30 -05:00
0525466708
back to ATOM_SHELL_INTERNAL_RUN_AS_NODE
2016-07-08 16:12:10 +02:00
5d1affed4b
ATOM_SHELL_INTERNAL_RUN_AS_NODE => ELECTRON_RUN_AS_NODE
2016-07-02 08:39:01 +02:00
1a51948f9c
add code launcher for windows bash
...
fixes #1704
2016-02-25 16:53:32 +01:00
Robo
Martin Aeschlimann
Alexandru Dima
ChaseKnowlden
kieferrm
XTY
Daniel Imms
Andrew Baumann
Daniel Imms
Benjamin Pasero
Aldo Fregoso
Benjamin Pasero
Joao Moreno