delorie.com/archives/browse.cgi | search |
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: | <81cec73805070716387b6acd83@mail.gmail.com> |
Date: | Thu, 7 Jul 2005 19:38:01 -0400 |
From: | Rex Eastbourne <rex DOT eastbourne AT gmail DOT com> |
Reply-To: | Rex Eastbourne <rex DOT eastbourne AT gmail DOT com> |
To: | Cygwin List <cygwin AT cygwin DOT com> |
Subject: | The perils of editing .bashrc |
Mime-Version: | 1.0 |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id j67NcCda007013 |
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? Thanks, Rex -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |