X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-5.8 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_TX
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
X-Received: by 10.224.138.148 with SMTP id a20mr10397650qau.38.1361999862220; Wed, 27 Feb 2013 13:17:42 -0800 (PST)
In-Reply-To: <13227.1361996106@freon.franz.com>
References: <15470 DOT 1361923720 AT relay DOT known DOT net>	<512E489F DOT 8060700 AT dronecode DOT org DOT uk>	<6514 DOT 1361987973 AT freon DOT franz DOT com>	<1977176204 DOT 20130227233752 AT mtu-net DOT ru>	<13227 DOT 1361996106 AT freon DOT franz DOT com>
Date: Wed, 27 Feb 2013 16:17:42 -0500
Message-ID: <CA+sc5mmn54WHcMp4Ycz7Lw8z9qe6aSvZ6GjU7JNo3fTcCxHg3w@mail.gmail.com>
Subject: Re: startxwin started bash does not read .bashrc or .bash_profile
From: Earnie Boyd <earnie AT users DOT sourceforge DOT net>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Wed, Feb 27, 2013 at 3:15 PM, Kevin Layer wrote:
> 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.

$HOME/.bashrc isn't always read.  It depends on how bash is executed.
If this is a --login you need $HOME/.bash_profile that sources
$HOME/.bashrc.

http://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html#Bash-Startup-Files

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

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