X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <683244.21792.qm@web34501.mail.mud.yahoo.com> References: <244882 DOT 68384 DOT qm AT web34508 DOT mail DOT mud DOT yahoo DOT com> <4B741CEB DOT 6070706 AT towo DOT net> <1ef5a52f1002110730v4325a8a0qd8e371019530a5da AT mail DOT gmail DOT com> <490452 DOT 20994 DOT qm AT web34508 DOT mail DOT mud DOT yahoo DOT com> Date: Fri, 12 Feb 2010 01:17:21 -0800 (PST) From: Neil Blue Reply-To: Neil Blue Subject: Re: .bashrc file not run To: John Morrison , cygwin AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 The ~/.bashrc file wasn't called by default and altering ~/.profile did fix the problem. The comments in /etc/profile seem to imply that ~/.bashrc should be run on a per user basis automatically, but this was not the case. ... # Setup some default paths. Note that this order will allow user installed # software to override 'system' software # If you wish to change the path for all users, it is recommended you edit # /etc/bash.bashrc # If you wish all future users to have some default setup, it is recommended you # edit /etc/skel/.bashrc # If you wish to change the path on a user by user basis, it is recommended you # edit ~/.bashrc ... /etc/skel/.bash_profile does have the code to call ~/.bashrc, but it doesn't seem to get used. ... # source the users bashrc if it exists if [ -e "${HOME}/.bashrc" ] ; then source "${HOME}/.bashrc" fi ... I still need to start bash without --login however as any settings such as PATH that are configured in ~/.bashrc are lost, but it does run the ~/.bashrc file. Neil ----- Original Message ---- From: John Morrison To: cygwin AT cygwin DOT com Sent: Fri, February 12, 2010 8:26:24 AM Subject: Re: .bashrc file not run ~/.bash_profile should already be setup to call ~/.bashrc it should have been in the base-files package which creates the /etc/skel files which should be copied when the user first log's on. AFAIK bash doesn't use a ~/.profile file. I *think* it's the KORN shell that does... do you mean /etc/profile? J. On Thu, February 11, 2010 4:28 pm, Neil Blue wrote: > Great, > > Thank you both. I now have .bash_profile calling ~/.bashrc. > > Just had a look at the ~/.profile script on my linux box and I can see > where it is making the call to the local ~/.bashrc file > > ... > # if running bash > if [ -n "$BASH_VERSION" ]; then > # include .bashrc if it exists > if [ -f "$HOME/.bashrc" ]; then > . "$HOME/.bashrc" > fi > fi > ... > > I guess I am too used to having this already set-up for me. > > Thanks again for the help. > > Cheers > Neil > > > > ----- Original Message ---- > From: Csaba Raduly > To: cygwin AT cygwin DOT com > Sent: Thu, February 11, 2010 3:30:15 PM > Subject: Re: .bashrc file not run > > On Thu, Feb 11, 2010 at 4:06 PM, Thomas Wolff wrote: >> On 11.02.2010 15:55, Neil Blue wrote: >> >> By design (and documentation), bash runs *only* .profile (and >> /etc/profile) >> if started as a "login shell". > > Not quite. > From "info bash" , Node: Bash Startup Files > > When Bash is invoked as an interactive login shell, or as a > non-interactive shell with the `--login' option, it first reads and > executes commands from the file `/etc/profile', if that file exists. > After reading that file, it looks for `~/.bash_profile', > `~/.bash_login', and `~/.profile', in that order, and reads and > executes commands from the first one that exists and is readable. > > > Note to Neil: .bashrc_profile is ignored by bash. You want .bash_profile > > Hope this helps. > -- > Life is complex, with real and imaginary parts > > -- > 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 > > > > > -- > 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 > > > -- 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 -- 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