X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: screen - doesn't call .bashrc at startup Date: Wed, 25 Jul 2007 16:26:49 +0100 Lines: 15 Message-ID: References: <5abc24640707250533l22ced282gd6332864ef96340a AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.70.2067 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 * Andrew Louie (Wed, 25 Jul 2007 08:33:36 -0400) > On 7/25/07, Thorsten Kampe wrote: > > Screen will *never ever* source your .bashrc, that's for sure. > > except when you source your .bashrc file from .bash_profile, and > thought it would be a neat trick to call screen from .bashrc so that > it will start up when you start cygwin..... Well, I guess that happened to a lot of people (including me). Anyway: it's still bash sourcing .bashrc and not screen sourcing .bashrc. Sourcing .bashrc from .bash_profile is actually the "correct" and recommended procedure. Thorsten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/