X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_TX X-Spam-Check-By: sourceware.org From: Kevin Layer To: cygwin@cygwin.com Subject: Re: startxwin started bash does not read .bashrc or .bash_profile In-reply-to: <1977176204.20130227233752@mtu-net.ru> References: <15470.1361923720@relay.known.net> <512E489F.8060700@dronecode.org.uk> <6514.1361987973@freon.franz.com> <1977176204.20130227233752@mtu-net.ru> Comments: In-reply-to Andrey Repin message dated "Wed, 27 Feb 2013 23:37:52 +0400." Date: Wed, 27 Feb 2013 12:15:06 -0800 Message-ID: <13227.1361996106@freon.franz.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Andrey Repin wrote: >> Greetings, Kevin Layer! >> >> > I know ~/.bashrc hasn't been read because my prompt is not changed and >> > my aliases are not there. >> >> That's just assumption. Not the first-hand knowledge. It may be true, or >> not... Best way to know is to place >> set -x >> around the start of the file and observe the results. That was one of the experiments I did, and I saw no evidence that any commands were executed. I even passed it as the argument to the invocation. As for the assumption, I understand that an error could have short-circuited the processing of my init file, but in the bash's that haven't read it, . .bashrc produces no errors *and* has my aliases and new prompt. Kevin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple