6074ca275b
Pass the user data dir to the browser environment service then derive all the paths we can based off that path like the global storage path which the vim extension uses to store history (otherwise it gets stored in the working directory from when code-server was spawned). Arguably the better solution is to use the userdata scheme but that won't work because the vim extension ignores the VS Code API. Fixes #1551. |
||
|---|---|---|
| .. | ||
| dev-image | ||
| image | ||
| release-image | ||
| build-test.sh | ||
| build.ts | ||
| ci.sh | ||
| clean.sh | ||
| code-server.sh | ||
| fmt.sh | ||
| lib.sh | ||
| lint.sh | ||
| release.sh | ||
| tsconfig.json | ||
| vscode.patch | ||
| vscode.sh | ||