startxwin started bash does not read .bashrc or .bash_profile

Christopher Faylor
Wed Feb 27 20:09:00 GMT 2013

On Wed, Feb 27, 2013 at 11:37:52PM +0400, Andrey Repin wrote:
>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.

**cgf checks the mailing list

Yep.  It really is the cygwin mailing list.

If someone is here, it is presumed that they want to use Cygwin so suggesting
non-Cygwin alternatives is really off-topic and )adjective deleted(.


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list