This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Use generic HOME environment variable for Windows if set #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Normally,
USERPROFILEis only the one environment variable which Windows applications use to determine home directory. A lot of tools supportHOMEand cross-common environment variable (git, etc.). Even Python interpreter checks for HOME before USERPROFILE.We have a few reported issues related to this problem. Our tool is written in Python but we have PlatformIO IDE extensions for Atom/VSCode. As result,
getHomeDirectorydiffers from Python'sos.path.expanduser.Sure, we can implement own
getHomeDirectoryin our Node.JS helper tools but I think this PR could be useful for other developers who use a common HOME environment variable.