Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

It's better to follow symlinks recursively in Linux launch script #14044

Closed
ZHOUYue67 opened this issue Oct 20, 2016 · 0 comments · Fixed by #14046
Closed

It's better to follow symlinks recursively in Linux launch script #14044

ZHOUYue67 opened this issue Oct 20, 2016 · 0 comments · Fixed by #14046
Assignees
Labels
linux Issues with VS Code on Linux
Milestone

Comments

@ZHOUYue67
Copy link
Contributor

ZHOUYue67 commented Oct 20, 2016

The Linux launch script (bin/code) of vscode finds VSCODE_PATH by resolving the path of itself:

VSCODE_PATH="$(dirname $(readlink $0))/.."

Some users might want to use symlinks that link to symlink of bin/code, then this script will fail to launch vscode, because it only follows one layer of symlinks. To solve this problem, simply add -f option to readlink to resolve the symlinks recursively:

VSCODE_PATH="$(dirname $(readlink -f $0))/.."

A pull request is on the way.

@ZHOUYue67 ZHOUYue67 changed the title It's better to follow symlink recursively in Linux launch script It's better to follow symlinks recursively in Linux launch script Oct 20, 2016
@Tyriar Tyriar added this to the October 2016 milestone Oct 20, 2016
@Tyriar Tyriar added the linux Issues with VS Code on Linux label Oct 20, 2016
@Tyriar Tyriar self-assigned this Oct 20, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
linux Issues with VS Code on Linux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants