delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-3.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_TX |
X-Spam-Check-By: | sourceware.org |
From: | Kevin Layer <layer AT known DOT net> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: startxwin started bash does not read .bashrc or .bash_profile |
In-reply-to: | <CA+sc5mmn54WHcMp4Ycz7Lw8z9qe6aSvZ6GjU7JNo3fTcCxHg3w@mail.gmail.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> <CA+sc5mmn54WHcMp4Ycz7Lw8z9qe6aSvZ6GjU7JNo3fTcCxHg3w AT mail DOT gmail DOT com> |
Comments: | In-reply-to Earnie Boyd <earnie AT users DOT sourceforge DOT net> message dated "Wed, 27 Feb 2013 16:17:42 -0500." |
Date: | Wed, 27 Feb 2013 14:16:42 -0800 |
Message-ID: | <28423.1362003402@relay.known.net> |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
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 |
Earnie Boyd wrote: >> 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. Did you read the original report and all the replies in the chain? ...it requires my .bashrc to be sourced (.bash_profile merely sources .bashrc). -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |