You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ZHOUYue67
added a commit
to ZHOUYue67/vscode
that referenced
this issue
Oct 20, 2016
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
The Linux launch script (
bin/code
) of vscode findsVSCODE_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 toreadlink
to resolve the symlinks recursively:VSCODE_PATH="$(dirname $(readlink -f $0))/.."
A pull request is on the way.
The text was updated successfully, but these errors were encountered: