Date: Sun, 21 Sep 2008 18:45:22 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Jeremy Chadwick <koitsu@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: Fwd: Re: Incorrect commandline history with bash Message-ID: <p06240801c4fc7c57b712@[128.113.24.47]> In-Reply-To: <20080921215255.GA9622@icarus.home.lan> References: <20080921215255.GA9622@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:52 PM -0700 9/21/08, Jeremy Chadwick wrote: > >Individual did not CC the mailing list on his response. > >----- Forwarded message from manish jain <unxfbsdi@gmail.com> ----- > > > > Thanks Jeremy. Sourcing .bash_profile from .bashrc solved the > > problem. For some reason, sourcing .bashrc from .bash_profile > > worked equally well with the version of Linux I was previously > > using. > > >> Regards >> Manish Jain >----- end message from manish jain <unxfbsdi@gmail.com> ----- I do not understand how that makes any difference. He had all his commands in .bashrc, and sourced it from .bash_profile. If he moves all his commands to .bash_profile, and then sources that from his .bashrc, then isn't the result exactly the same? Either way, all commands should be executed no matter how bash starts up. I only mention this because my .bash_profile sources my .bashrc, and has done so on many different platforms for the past 18 years, and I've never had a problem with it. Although in my case it checks for and sources $HOME/.bashrc while he was using ~/.bashrc. Not only my .bash_profile, but every .bash_profile and .bashrc at RPI was setup this way. Tens of thousands of users, and I've never heard of anyone who had a problem with it. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240801c4fc7c57b712>