X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_05,KHOP_THREADED,RP_MATCHES_RCVD,TW_TX X-Spam-Check-By: sourceware.org Message-ID: <512E29CA.40002@cs.umass.edu> Date: Wed, 27 Feb 2013 10:44:10 -0500 From: Eliot Moss Reply-To: moss@cs.umass.edu User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: startxwin started bash does not read .bashrc or .bash_profile References: <15470.1361923720@relay.known.net> <512D7040.7080905@gmail.com> <26949.1361935259@relay.known.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 2/27/2013 10:36 AM, Robert Pendell wrote: Dear Robert -- I think the original poster's concern was not the general working of bash with .bash_profile and .bashrc, but the specific behavior when bash is started by an instance of mintty which itself is started by the X windows server in .startxwinrc -- a behavior that seems at variance with the normal bash startup behavior. My sense of what you wrote was that it reported testing running a new bash from bash, which is not the situation of concern ... Regards -- Eliot Moss -- 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