Support symbolic link folders in areas like debug, extensions

• VSCode Version: 1.16.1
• OS Version: macOS sierra 10.12

Steps to Reproduce:

1. Open a empty workspace
2. Create a file and create a symlink to this file in workspace.
3. On opening the file, the linked file will be open in the editor. The path (on hovering over the opened file name) will be shown for the symlink and opening the file in Finder by right clicking will also open the symlink’s parent folder.

The issue with this is it also causes inconsistency with Git markers in enhanced scrollbar and all extensions which operate on open file (like gitlens for git blame).

There should be a editor property to configure this path to be set as original file’s path or the symlink’s path.

Reproduces without extensions: Yes

[koliyo]

Wow, this issue is causing me so much headaches due to VS code opening same file in multiple tabs with multiple paths (real path and symlinked path), and other problems as well

[ghost]

This also occurs if your project is on a different partition and you have a symlink to the parent directory of the the project folder. vscode will follow the symlink path instead of the real path.

Say you have ~/projects -> /mnt/data/projects vscode will open a file using this path ~/projects/pro1/file instead of using the absolute path.

This prevents git markings from showing and you have to manually refresh the source control to see the changed files list.

My work around is replacing the project path from “.” to the absolute path to the project in the workspace file:

"folders": [
    {
        "path": "/mnt/projects/pro1"
    }
],

but unfortunately I can’t commit this to the repo.