is anyone using VSCode and/or Webstorm with WSL fo...
# suitescripts
stalbert
04/03/2019, 5:43 PMis anyone using VSCode and/or Webstorm with WSL for doing SuiteScript development?
j
jkabot
04/03/2019, 5:44 PMI am using vscode and WSL
j
JohnnyC
04/03/2019, 5:48 PMIs there a plugin for VSCode for SDF?
a
aerin
04/03/2019, 6:03 PMI have used VSCode, but there is no plugin for it
aerin
04/03/2019, 6:04 PMthe NS plugin for eclipse is pretty useless anyway, I rarely actually use it even in eclipse
j
jkabot
04/03/2019, 6:15 PMthere's https://github.com/mark-keaton/NetSuiteSDF from @mkeaton
m
mkeaton
04/03/2019, 6:24 PMYeah, try it out. We have a major release ready. It’s just in testing.
s
stalbert
04/03/2019, 6:46 PM@jkabot I run into issues using WSL(bash.exe) as the integrated terminal and doing
gitgitstalbert
04/03/2019, 6:46 PMI'll have situations where I can't switch branches do to permission problems
stalbert
04/03/2019, 6:46 PMI do keep my code on a windows partition and access it via the terminal
/mnt/c/xxxstalbert
04/03/2019, 6:47 PMwondering if you've seen any errors either from doing things from the git commandline or from the VSCode git UI integration
j
jkabot
04/03/2019, 7:00 PMIt's correct that the vs code for windows does not (and afaik cannot) use the wsl linux git
I was actually looking into this yesterday while trying to figure out an issue with some git precommit hooks.
They worked when using git from the command line (in wsl), but not using the vs code ui.
https://github.com/Microsoft/vscode/issues/9502
jkabot
04/03/2019, 7:01 PMfrom what I understand the workaround is to have vs code make calls to https://github.com/andy-5/wslgit
s
stalbert
04/03/2019, 7:14 PMI saw mention of wslgit also - and I hesitate to throw another layer in, especially given people saying it's slow. I might have to give it a try as it can't be worse than the conflicts between windows/wsl I'm going through?
stalbert
04/03/2019, 7:16 PM@mkeaton I'll try it out once your major release is... released?
m
mkeaton
04/03/2019, 7:42 PMSure. I’ll post once @chris and I agree it’s ready. I’m waiting on some 2019.1 stability after this one for a quick release, and hopefully gearing up for a rewrite for the Node CLI
2 Views