atom-community / atom-community/atom-script

No longer using Go script's directory as current working directory

Open
#1,007 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
730
Forks
264
PR merge metrics
No merged PRs in 30d

Description

Several weeks ago, executing Go scripts would use the script's directory as the Current Working Directory, thereby ensuring that any data files were available. With the most recent version (3.8.1), the CWD has changed to GOPATH's src directory instead. As a result, it's looking for the data files in the wrong place.

Could the original behaviour be restored? Putting a specific project's data files in the src/ root is a bad idea (doesn't follow the GOPATH convention).

NOTE: I have no idea which version introduced this, because I don't know what version I was using before the upgrade, and I haven't found a way to downgrade packages.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.