microsoft / microsoft/vscode-remote-release

Indistinguishable folder name in Windows "Recent Workspaces"

Open
#3,937 10 comments 9 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Nov 6, 2020.

bug containers
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

I have multiple remote containers running in Docker in WSL2.

The contents is located under /home/<user>/dev/<project> (or \\wsl$\Ubuntu-20.04\home\<user>\dev\<project>).
The projects have no *.code-workspace file and are configured using "workspaceFolder": "/workspace", in devcontainer.json.

After opening the projects, the Windows "Recent Workspaces" section of the task bar menu shows entries with the same name: workspace [Dev Container], even the tool tip text doesn't help to distinguish the two folders as it uses some sort of hash (e.g. "workspace vscode-remote://dev-container+5c5c77736...263/").

It would be much better to have the Linux folder as the title of the workspace folder like it is done for example in SSH remote targets. If this isn't feasible or doesn't make sense, at least the tool tip should show some information that helps the user to identify the folder name. Remote Explorer inside VS Code shows usable names (see below).

Task bar menu:
image

Remote Explorer:
image

If you want to reproduce this, the two projects are:
https://github.com/UncleSamSwiss/ioBroker.loxone
https://github.com/UncleSamSwiss/ioBroker.i2c

Version info:
Version: 1.50.1 (system setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.