tag:blogger.com,1999:blog-23664930.post8247297539238685659..comments2023-07-04T11:38:44.389-04:00Comments on { ParsedContent };: OSx and the bashrcNumberwhunhttp://www.blogger.com/profile/17039719920081966779noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-23664930.post-43700256761985144702012-03-07T18:27:21.178-05:002012-03-07T18:27:21.178-05:00Thanks for the input Tom, I appreciate it. I have...Thanks for the input Tom, I appreciate it. I have been working on Linux/Unix for about 15 years now and honestly have not really separated my shell information into the different files as you mentioned. <br /><br />When I started ages ago I was taught to create my rc file and put all of my configuration information into there. I am so used to putting my settings into the rc file that it would be quite the change to separate it. I do keep it organized, separating information and making notes with comments (as is proper) so I know what is for what. <br /><br />I will have to read the link you provided and do some reading on my own to learn the proper way things are handled. I guess its just complacent laziness that I thought I already knew, but hey, I am not above admitting I was wrong and learning the correct information. :) <br /><br />Regards,<br /><br />JeffNumberwhunhttps://www.blogger.com/profile/17039719920081966779noreply@blogger.comtag:blogger.com,1999:blog-23664930.post-29204618489321273122012-03-07T17:40:57.829-05:002012-03-07T17:40:57.829-05:00It's not correct that the OS X behavior differ...It's not correct that the OS X behavior differs from Linux. You need to learn the difference between a login shell and a non-login interactive shell. Terminal runs a login shell, which reads .bash_profile or .profile, not .bashrc. The correct way to get your desired behavior is to create a .bash_profile that defines the behavior you want unique to login shells, and at its end to have it source your .bashrc.<br /><br />Roughly speaking, you probably want to have settings such as your PATH and other environment variables in the profile, and command aliases and definitions in your .bashrc.<br /><br />A number of *exchange posts discuss this, e.g.:<br /><a href="http://stackoverflow.com/questions/3484429/profile-and-bashrc-doesnt-work-on-my-mac" rel="nofollow">profile-and-bashrc-doesnt-work-on-my-mac</a>.<br /><br />I know this is an old post, but I thought it was worth clarifying since others may find it.Tom Loredohttps://www.blogger.com/profile/01148329447605438040noreply@blogger.com