Ensure ~/.recap can be sourced from anywhere #56
Merged
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
Sourcing ~/.recap from outside the home directory fails to generate the .recap-env-export file correctly because it expects to find .env in the current directory. This fix ensures we read ~.env and generate ~/.recap-env-export correctly. I came across this problem when using the whenever gem to generate my crontab. It generate a command similar to /bin/bash -l -c 'my-command' which I tried to run from the command line. Running it in a directory outside of ~ fails due to the problem mentioned above. *NOTE* The key part of that command is '-l' which tells bash to load ~/.profile (among other things).
tomafro
added a commit
that referenced
this pull request
May 11, 2012
…ecap-env-export Ensure ~/.recap can be sourced from anywhere
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sourcing ~/.recap from outside the home directory fails to generate the
.recap-env-export file correctly because it expects to find .env in the
current directory.
This fix ensures we read ~/.env and generate ~/.recap-env-export
correctly.
I came across this problem when using the whenever gem to generate my
crontab. It generate a command similar to /bin/bash -l -c 'my-command'
which I tried to run from the command line. Running it in a directory
outside of ~ fails due to the problem mentioned above. NOTE The key
part of that command is '-l' which tells bash to load ~/.profile (among
other things).