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.

Sign up for GitHub

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

Jump to bottom

Should this follow "source" calls? #2

Open
edenman opened this issue May 5, 2017 · 2 comments
Open

Should this follow "source" calls? #2

edenman opened this issue May 5, 2017 · 2 comments

Comments

@edenman
Copy link

edenman commented May 5, 2017

My ~/.bash_profile just has one line: source .bashrc. For now I've just changed .osx-env-sync.sh to read from that file, but that's obviously not ideal. Would be cool if we could follow the chain of source calls. I could imagine some people splitting up their bashrc into several files based on area of concern, for instance.
@plijnzaad
Copy link

I would be in favour of adding this, but it's not trivial (the sourced file could itself source yet more files in turn).

Other than that: kudos to @ersiner for this nice little life-saver

@jiacai2050
Copy link

jiacai2050 commented Nov 10, 2019 •
edited
Loading

I have a similar config, here is my solution:

source ~/.bash_profile
/usr/bin/env | while IFS=' =' read envvar ignorevalue; do
  launchctl setenv ${envvar} ${!envvar}
done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edenman @jiacai2050 @plijnzaad