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

Do not evaluate /etc/bashrc on non-interactive shells #109

Merged
merged 3 commits into from
Oct 17, 2018

Conversation

marsam
Copy link
Contributor

@marsam marsam commented Oct 14, 2018

No description provided.

@marsam marsam force-pushed the feature/update-bashrc-config branch from 2fcf423 to dff88ee Compare October 14, 2018 15:39
@@ -52,6 +52,9 @@ in
# /etc/bashrc: DO NOT EDIT -- this file has been generated automatically.
# This file is read for interactive shells.

# If not running interactively, don't do anything
[[ $- != *i* ]] && return
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Breaking out here means the nix tools won't be in PATH over a non interactive ssh connection (eg. distributed builds) Basic things like environment variables should always be configured.

Copy link
Contributor Author

@marsam marsam Oct 17, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I realized it later, I've placed this early return below the basic setup 1a786eb

Setting PATH and environment setup is required in non-interactive shells
Copy link
Owner

@LnL7 LnL7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@LnL7 LnL7 merged commit e6a698a into LnL7:master Oct 17, 2018
@marsam marsam deleted the feature/update-bashrc-config branch October 18, 2018 00:30
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