X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Problem with aliases in bash as login shell Date: Fri, 21 Nov 2008 15:46:03 +0100 Message-ID: <574BF80562AF37419EA4B003C90D756D06E28550@EXCHANGE1.belgium.fhm.de> In-Reply-To: From: "Morche Matthias" To: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id mALEkrUg027084 Hi Ryan, > -----Original Message----- > From: cygwin-owner AT cygwin DOT com ... > When bash is started with the "-l" (that's an 'L') flag, aliases that > I've defined in .bashrc don't take effect. My .bash_profile includes a > call to .bashrc, and I know that .bashrc is being executed because ... I bet Your line with the call of .bashrc from .bash_profile looks like .bashrc change it to . .bashrc and it will do what You intend and then RTFM for an explanation :-) best regards, matthias -- 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/