Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: .bashrc not working (and yes I've read the FAQ etc as you'll see) Date: Fri, 18 Feb 2005 14:32:09 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Jesper Vad Kristensen" To: "Steve Mayes" , X-OriginalArrivalTime: 18 Feb 2005 13:32:09.0442 (UTC) FILETIME=[3EF94420:01C515BE] X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j1IDWMY5014332 Steve wrote: >Forgive the defensive addendum but I've no wish to be either flamed or >ignored when I've tried available pathways to solving this. Must ... resist ... urge ... to .... flame ... }:-)> >Situation: > >.bashrc not working and yes my $home variable is correctly >defined but I >put a copy of .bashrc into / anyway just in case. >The --login and -i switches are used. >I even used the --rcfile switch and pointed it directly to my .bashrc >file at which point cygwin just bombs out. > >.bashrc file contains only the line > >Alias ls='ls -al --color=auto' > >I even made .bashrc executable using the command chmod +x >(just in case) >but this changed none of the behaviour. What am I missing. I'm pretty much missing a proper description of the problem. Whaddaya mean ".bashrc not working"? And what's "cygwin just bombs out" supposed to mean - is it some sort of new hacker language or technical term I didn't pick up on? What's your entry in /etc/passwd say? Regards, Jesper Vad Kristensen -- 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/