This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: startxwin started bash does not read .bashrc or .bash_profile
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin at cygwin dot com
- Cc: layer at known dot net
- Date: Wed, 27 Feb 2013 17:55:43 +0000
- Subject: Re: startxwin started bash does not read .bashrc or .bash_profile
- References: <15470.1361923720@relay.known.net>
- Reply-to: cygwin at cygwin dot com
On 27/02/2013 00:08, Kevin Layer wrote:
> If I put this into .startxwinrc:
>
> mintty /usr/bin/bash.exe --login -i
>
> the resulting shell does not read .bash_profile. If I put
>
> mintty /usr/bin/bash.exe -i
>
> it doesn't read .bashrc.
I've tried to reproduce this, but it seem to work ok for me.
How can are you checking if ~/.bashrc has been read? Have you tried using bash
-v to check what bash is reading?
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?
> 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.
--
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