Under Windows after installing code-d ( and workspace-d ), it will ask to install (compile) DCD, fmt, scanner. When it tries to Compile ( install ) DCD etc:
And here it will simply stall... because git.exe is not part of the systems path. In fact it is known to VSC with the "git.path" but because workspace's simple assumes it public known, it will always fail. Is it possible to add to code-d the ability to manual set the git path as a setting, so it can correctly use git from any source that is not in the path?
There is another reason as to why a manual path in settings is interesting: Version conflicts.
Technically, we can simply reuse the VSC "git.path" variable for this ( if it has been set ), so there is no need for a custom one. Because without this, its back to manually getting and compiling.
Git is installed as Portable, Visual Studio Code also a portable app ( PortableApps ). Git is linked correctly to VSC in the settings:
Under Windows after installing code-d ( and workspace-d ), it will ask to install (compile) DCD, fmt, scanner. When it tries to Compile ( install ) DCD etc:
And here it will simply stall... because git.exe is not part of the systems path. In fact it is known to VSC with the "git.path" but because workspace's simple assumes it public known, it will always fail. Is it possible to add to code-d the ability to manual set the git path as a setting, so it can correctly use git from any source that is not in the path?
There is another reason as to why a manual path in settings is interesting: Version conflicts.
Technically, we can simply reuse the VSC "git.path" variable for this ( if it has been set ), so there is no need for a custom one. Because without this, its back to manually getting and compiling.