Date: Wed, 27 Feb 2013 23:37:52 +0400
From: Andrey Repin <anrdaemon@freemail.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <1977176204.20130227233752@mtu-net.ru>
To: Kevin Layer <layer@franz.com>, cygwin@cygwin.com
Subject: Re: startxwin started bash does not read .bashrc or .bash_profile
In-Reply-To: <6514.1361987973@freon.franz.com>
References: <15470.1361923720@relay.known.net> <512E489F.8060700@dronecode.org.uk> <6514.1361987973@freon.franz.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Greetings, Kevin Layer!

> I know ~/.bashrc hasn't been read because my prompt is not changed and
> my aliases are not there.

That's just assumption. Not the first-hand knowledge. It may be true, or
not... Best way to know is to place
set -x
around the start of the file and observe the results.

>>> This is also a really odd place to start mintty.  Why start it as a side
>>> effect of the unrelated action starting the X server?

> This is merely an example, the simplest one to reproduce the failure.
> It's not how I want to use startxwin.

>>> > My ultimate goal is to use ssh-agent/ssh-add to make life easier, but
>>> > it requires my .bashrc to be sourced (.bash_profile merely sources
>>> > .bashrc).
>>> 
>>> If you are going to work with both mintty and X clients, which will not
>>> naturally have a common parent ssh-agent process to inherit from, you might
>>> want to investigate the keychain package.

> I'm unfamiliar with that.  Thanks for the pointer.

Or simply use PuTTY and PageAnt.


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 27.02.2013, <23:35>

Sorry for my terrible english...


--
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