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.

Sign up for GitHub

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

Jump to bottom

Launching tasks fails when cwd is utilized #106988

Closed
LoeDK opened this issue Sep 18, 2020 · 3 comments
Closed

Launching tasks fails when cwd is utilized #106988

LoeDK opened this issue Sep 18, 2020 · 3 comments
Assignees
@alexr00
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders variable-resolving verified Verification succeeded
Milestone
September 2020

Comments

@LoeDK
Copy link

LoeDK commented Sep 18, 2020

  • VSCode Version:
    code-insiders/stable 1.50.0-1600363724 amd64
  • OS Version:
    Ubuntu 18.04

Steps to Reproduce:

  1. create a launch task that utilizes "${file}"

Expectation:
"${file}" is absolute: /home/user/.../file.ext

Actual Result:
"${file}" is ~/...

In my case, this leads to errors because ~/ cannot be resolved by that process.

Does this issue occur when all extensions are disabled?: Yes
@LoeDK LoeDK mentioned this issue Sep 18, 2020
Closed
@LoeDK
Copy link
Author

LoeDK commented Sep 18, 2020

@alexr00 this may be related to your latest fix.

@alexr00
Copy link
Member

alexr00 commented Sep 18, 2020

Duplicate of #106877

@alexr00 alexr00 marked this as a duplicate of #106877 Sep 18, 2020
@alexr00 alexr00 closed this as completed Sep 18, 2020
@alexr00 alexr00 added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 18, 2020
@alexr00 alexr00 reopened this Sep 18, 2020
@alexr00 alexr00 added variable-resolving and removed *duplicate Issue identified as a duplicate of another issue(s) labels Sep 18, 2020
@alexr00 alexr00 self-assigned this Sep 18, 2020
@alexr00 alexr00 added the bug Issue identified by VS Code Team member as probable bug label Sep 18, 2020
@alexr00 alexr00 added this to the September 2020 milestone Sep 18, 2020
@alexr00
Copy link
Member

alexr00 commented Sep 18, 2020

Looks like I missed a spot...

@alexr00 alexr00 mentioned this issue Sep 21, 2020
Closed
@connor4312 connor4312 added the verified Verification succeeded label Oct 1, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@alexr00 alexr00

Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders variable-resolving verified Verification succeeded
Projects
None yet
Milestone
September 2020
Development

No branches or pull requests
4 participants
@connor4312 @LoeDK @alexr00 and others