Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <01ab01c02a44$ea9c04d0$cf01010a@in.teamp.com>
From: "Erik Nolte" <enolte@campuspipeline.com>
To: "Earnie Boyd" <earnie_boyd@yahoo.com>,
        "Masterson Dave" <dmasters@rational.com>, <cygwin@sources.redhat.com>
References: <20000929182535.7375.qmail@web124.yahoomail.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

> > 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@sourceware.cygnus.com