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.

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

Export $HOME by default #217

Closed
wants to merge 0 commits into from
Closed

Export $HOME by default #217

wants to merge 0 commits into from

Conversation

petersohn
Copy link
Contributor

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.

@gittup
Copy link
Owner

gittup commented Jan 20, 2015

Merged - thanks!

-Mike

On Fri, Jan 2, 2015 at 2:15 PM, Péter Szabados notifications@github.com
wrote:

I am trying to use tup together with rtags
https://github.com/Andersbakken/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.

You can merge this Pull Request by running

git pull https://github.com/petersohn/tup master

Or view, comment on, or merge it at:

#217
Commit Summary

  • Export $HOME by default

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#217.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants