Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <01ab01c02a44$ea9c04d0$cf01010a@in.teamp.com> From: "Erik Nolte" To: "Earnie Boyd" , "Masterson Dave" , References: <20000929182535 DOT 7375 DOT qmail AT web124 DOT yahoomail DOT com> Subject: Re: /etc/profile in BASH Date: Fri, 29 Sep 2000 12:41:44 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > > I didn't realize that a login BASH doesn't execute ~/.bashrc. Be that as it > > may, I think it should be the decision of ~/.bash_profile (or ~/.profile) > > whether to execute ~/.bashrc -- *NOT* /etc/profile. Putting this into > > /etc/profile makes it too BASH-centric. What about the [T]CSH users? Also, > > what about ~/.bash_login files (as described in the MAN page)? > > > > IIRC [t]csh doesn't user /etc/profile. Use the source, Luke. (tm) But sh and ksh do. I don't want my sh's executing .bashrc and failing on things like alias and 'export var=..." - Erik -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com