Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	Andrew Schulman <andrex AT alumni DOT utexas DOT net>
Subject:	Re: The perils of editing .bashrc
Date:	Thu, 07 Jul 2005 19:48:11 -0400
Lines:	21
Message-ID:	<dakevr$4g5$1@sea.gmane.org>
References:	<81cec73805070716387b6acd83 AT mail DOT gmail DOT com>
Mime-Version:	1.0
User-Agent:	KNode/0.9.1
X-Archive:	encrypt
X-IsSubscribed:	yes

> Is it advisable to edit one's .bashrc? I'd like to put in a bunch of
> customizations, aliases, etc., but I'm intimidated by the message
> saying that my .bashrc will not be updated by setup.exe if I modify
> it. Does this mean that I'll have to put in changes for new programs
> manually? If so, how can I customize my shell without losing
> setup.exe's automation?

I'm not familiar with that message from setup, but your .bashrc is yours, to
do with as you please.  By all means, customize it to create a shell
environment to your liking.

setup should _never_ mess with your ~/.bashrc.  That file belongs to you. 
Setup may adjust /etc/profile and /etc/bash.bashrc, which provide the
system-wide defaults that get executed before your .bashrc.

See also the bash man page, "INVOCATION", to see which system and user
startup files get executed in what order.

Good luck,
Andrew.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -