X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,TW_MK,TW_TX X-Spam-Check-By: sourceware.org Message-ID: <512E2F7D.1030305@cs.umass.edu> Date: Wed, 27 Feb 2013 11:08:29 -0500 From: Eliot Moss Reply-To: moss AT cs DOT umass DOT 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 AT cygwin DOT com Subject: Re: startxwin started bash does not read .bashrc or .bash_profile References: <15470 DOT 1361923720 AT relay DOT known DOT net> <512D7040 DOT 7080905 AT gmail DOT com> <26949 DOT 1361935259 AT relay DOT known DOT net> In-Reply-To: <26949.1361935259@relay.known.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dear Kevin (et al.) -- I use StartXWin all the time, and start bash from an xterm, and the startup reading of .bash_profile, etc., proceeds as documented. Thinking it might be something about mintty, I tested that as well, with --login and with just -i, and it all works as expected, reading the proper startup files. Two things occur to me. One is that I struggle some with .startxwinrc, etc., until I realized that my usual scripts have not been run so my usual paths are not set. I needed an explicit setting of PATH in my .startxwinrc file, like this: PATH="${PATH}:/usr/bin" However, if mintty and bash are both running, then that is probably not your issue. What I do wonder about is the setting of HOME. In your email you wrote out *Windows* versions of the paths. My HOME reads /home/Eliot when I do echo $HOME in bash. While cygwin can use Windows paths in some cases, the whole situation can be sensitive and surprising. So this also leads me to wonder if you have the cygwin passwd and group files set up right. You might want to look into /etc/passwd and /etc/group. See the programs mkpasswd and mkgroup, which are there to help build proper versions of those files. Finally, did this start as a result of an upgrade of cygwin or of cygwin X server related programs or files? That would be a helpful clue (to the maintainers, not to me :-) ). Regards -- Eliot -- 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