X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20110406100426.GA5859@jethro.local.lan> References: <4D9B913F DOT 3070303 AT cygwin DOT com> <20110406100426 DOT GA5859 AT jethro DOT local DOT lan> Date: Thu, 7 Apr 2011 07:00:54 +0100 Message-ID: Subject: Re: .profile not sourced? From: Andy Koppe 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: List-Unsubscribe: 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 On 6 April 2011 11:04, David Sastre wrote: >> > On 4/5/2011 4:47 PM, philippe roux wrote: >> >> I have a file ~/.profile which contains some alias like >> >> and ./bash_profile file containing the lines > > When using bash as a login shell, the existence of .bash_profile > prevents from .profile being sourced. True, but Philippe said he had this in .bash_profile: # source the users profile if it exists if [ -f "${HOME}/.profile" ] ; then source "${HOME}/.profile" fi Might be an idea for base-files actually, allowing for bash-specific settings in .bash_profile while having settings common across shells in .profile. Andy -- 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