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
Message-ID: <32553.84.246.168.11.1120808042.squirrel@mail.morrison.mine.nu>
In-Reply-To: <Pine.GSO.4.61.0507072005420.29317@slinky.cs.nyu.edu>
References: <81cec73805070716387b6acd83 AT mail DOT gmail DOT com>     <Pine DOT GSO DOT 4 DOT 61 DOT 0507072005420 DOT 29317 AT slinky DOT cs DOT nyu DOT edu>
Date: Fri, 8 Jul 2005 08:34:02 +0100 (BST)
Subject: Re: The perils of editing .bashrc (Attn: base-files maintainer)
From: "John Morrison" <john AT morrison DOT mine DOT nu>
To: cygwin AT cygwin DOT com
Reply-To: john AT morrison DOT mine DOT nu
User-Agent: SquirrelMail/1.4.4
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit

On Fri, July 8, 2005 1:12 am, Igor Pechtchanski said:
> On Thu, 7 Jul 2005, Rex Eastbourne wrote:
>
>> 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?
>
> What Andrew said.  Setup will never touch the .bashrc in your home
> directory, whether you modify it or now.  The severe-sounding warning you
> saw really refers to /etc/skel/.bashrc (copied to every new user's
> directory, which is apparently what the base-files maintainer didn't count
> on).  So yes, do go ahead and customize it -- that's what it's there for.
>
> To the base-files maintainer: John, could you maybe tone the warning down
> a bit?  Perhaps simply putting the following would be enough (and
> certainly wouldn't sound as scary to new users):

Sure - I certainly didn't intent to scare people!

> "To pick up the latest recommended .bashrc content, look in
> /etc/defaults/etc/skel/.bashrc.  Modifying /etc/skel/.bashrc directly
> would prevent setup from updating it".
>
> I would even borrow Andrew's phrase and say "This is the default .bashrc
> file.  By all means, customize it to create a shell environment to your
> liking." somewhere in the top comments.

I need to do a new release.  I should be able to over the weekend.

J.


--
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/