www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ide - VSCode DLS in offline environment?

reply Rel <relmail rambler.ru> writes:
I'm doing all development in offline environment, so my computer 
doesn't have internet access So I downloaded and installed latest 
DMD, downloaded and installed VSCode extension "VSCode DLS", 
downloaded DLS executable from github and put it into DMD's bin 
folder. When I try to create and edit d-file in VSCode i get the 
error:

Starting client failed
Error: unsupported server configuration {
     "command":""
}

at main.js:356:35

How can I fix this? Also how do I install dub packages in offline 
environment?
Aug 14 2018
parent reply Laurent =?UTF-8?B?VHLDqWd1aWVy?= <laurent.treguier.sink gmail.com> writes:
On Tuesday, 14 August 2018 at 11:46:22 UTC, Rel wrote:

 I'm doing all development in offline environment, so my 
 computer doesn't have internet access So I downloaded and 
 installed latest DMD, downloaded and installed VSCode extension 
 "VSCode DLS", downloaded DLS executable from github and put it 
 into DMD's bin folder. When I try to create and edit d-file in 
 VSCode i get the error:

 Starting client failed
 Error: unsupported server configuration {
     "command":""
 }

 at main.js:356:35

 How can I fix this? Also how do I install dub packages in 
 offline environment?


If you dowloaded the dls executable yourself, you will have to 
set d.dlsPath in VSCode's settings to executable's ful' path so 
it can find it.
If you already did it, then I have yet another bug to fix...
If this is the case, can you tell me what OS you're using?

Regarding dub packages, I don't know... Most projects are on 
github or gitlab though, so you should be able to dowload their 
sources from there.
Aug 14 2018
parent reply Rel <relmail rambler.ru> writes:
On Tuesday, 14 August 2018 at 14:44:49 UTC, Laurent Tréguier 
wrote:

 On Tuesday, 14 August 2018 at 11:46:22 UTC, Rel wrote:

 I'm doing all development in offline environment, so my 
 computer doesn't have internet access So I downloaded and 
 installed latest DMD, downloaded and installed VSCode 
 extension "VSCode DLS", downloaded DLS executable from github 
 and put it into DMD's bin folder. When I try to create and 
 edit d-file in VSCode i get the error:

 Starting client failed
 Error: unsupported server configuration {
     "command":""
 }

 at main.js:356:35

 How can I fix this? Also how do I install dub packages in 
 offline environment?


 If you dowloaded the dls executable yourself, you will have to 
 set d.dlsPath in VSCode's settings to executable's ful' path so 
 it can find it.
 If you already did it, then I have yet another bug to fix...
 If this is the case, can you tell me what OS you're using?

 Regarding dub packages, I don't know... Most projects are on 
 github or gitlab though, so you should be able to dowload their 
 sources from there.


Okey, I think it found the dls.exe as it was in the Path 
environment variable. I tried adding the full path to it via 
"d.dlsPath" setting, but it doesn't start the client either 
without any log messages. I'm on Windows and I'm using the latest 
version on VSCode.
Aug 14 2018
parent reply Laurent =?UTF-8?B?VHLDqWd1aWVy?= <laurent.treguier.sink gmail.com> writes:
On Tuesday, 14 August 2018 at 18:35:24 UTC, Rel wrote:

 Okey, I think it found the dls.exe as it was in the Path 
 environment variable. I tried adding the full path to it via 
 "d.dlsPath" setting, but it doesn't start the client either 
 without any log messages. I'm on Windows and I'm using the 
 latest version on VSCode.


It doesn't look in the path to start dls, it should be checking 
only two paths by default: 
`%LOCALAPPDATA%\dub\packages\.bin\dls-latest\dls.exe` and 
`%LOCALAPPDATA%\dub\packages\.bin\dls.exe`.
When you say "without any log messages", do you mean that you are 
still getting the same error message, or that you are not even 
getting any error message at all ?
Aug 14 2018
parent reply Rel <relmail rambler.ru> writes:
On Tuesday, 14 August 2018 at 22:15:15 UTC, Laurent Tréguier 
wrote:

 It doesn't look in the path to start dls, it should be checking 
 only two paths by default: 
 `%LOCALAPPDATA%\dub\packages\.bin\dls-latest\dls.exe` and 
 `%LOCALAPPDATA%\dub\packages\.bin\dls.exe`.
 When you say "without any log messages", do you mean that you 
 are still getting the same error message, or that you are not 
 even getting any error message at all ?


Okey, so I put the dls executable to LOCALAPPDATA and it seems to 
work now, thanks! I understand that this thing is cased by my own 
work-place restrictioons, but maybe this thing should be noted in 
the package documentation somewhere.

If I was setting the dlsPath manually, I got the empty console 
window without any messages and code completion wasn't working, 
only syntax highlighting, so I suppose the DLS wasn't started 
correctly.
Aug 14 2018
parent Laurent =?UTF-8?B?VHLDqWd1aWVy?= <laurent.treguier.sink gmail.com> writes:
On Wednesday, 15 August 2018 at 06:59:25 UTC, Rel wrote:

 Okey, so I put the dls executable to LOCALAPPDATA and it seems 
 to work now, thanks! I understand that this thing is cased by 
 my own work-place restrictioons, but maybe this thing should be 
 noted in the package documentation somewhere.


This shouldn't be necessary, but I'll put something in the README 
in case other people stumble across this too.


 If I was setting the dlsPath manually, I got the empty console 
 window without any messages and code completion wasn't working, 
 only syntax highlighting, so I suppose the DLS wasn't started 
 correctly.


This is really strange, out of all the things that I test, this 
is the one I'm testing the most, since I'm using this setting to 
test dls debug builds when working on it.
Aug 15 2018