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.
I am trying to use tup together with rtags. It is a client/server based indexer for C/C++ that uses libclang for parsing the source files. To know the proper compilation flags for the source files, either a compilation database can be used (which is unfortunately not supported by tup) or a script can be used to hijack the compiler. The script contacts the server and tells it the compilation flags before calling the real compiler. The communication with the server is done via a Unix domain socket that is in the user's home directory.
This script can only run properly from tup if the HOME environment variable is exported, otherwise it cannot contact the server. Since it is should not be project specific whether I want to use rtags or not, it would be better if HOME would be exported by default. It is generally safe to export HOME because it does not tend to change much. So I added HOME to the environment variables exported by default.