From: Kevin Layer <layer@known.net>
To: cygwin@cygwin.com
Subject: Re: startxwin started bash does not read .bashrc or .bash_profile
Date: Wed, 27 Feb 2013 22:16:00 -0000 [thread overview]
Message-ID: <28423.1362003402@relay.known.net> (raw)
In-Reply-To: <CA+sc5mmn54WHcMp4Ycz7Lw8z9qe6aSvZ6GjU7JNo3fTcCxHg3w@mail.gmail.com>
Earnie Boyd wrote:
>> On Wed, Feb 27, 2013 at 3:15 PM, Kevin Layer wrote:
>> > That was one of the experiments I did, and I saw no evidence that any
>> > commands were executed. I even passed it as the argument to the
>> > invocation.
>> >
>> > As for the assumption, I understand that an error could have
>> > short-circuited the processing of my init file, but in the bash's that
>> > haven't read it,
>> >
>> > . .bashrc
>> >
>> > produces no errors *and* has my aliases and new prompt.
>>
>> $HOME/.bashrc isn't always read. It depends on how bash is executed.
>> If this is a --login you need $HOME/.bash_profile that sources
>> $HOME/.bashrc.
Did you read the original report and all the replies in the chain?
...it requires my .bashrc to be sourced (.bash_profile merely sources
.bashrc).
--
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
next prev parent reply other threads:[~2013-02-27 22:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 0:08 Kevin Layer
2013-02-27 2:32 ` Arthur Tu
2013-02-27 3:21 ` Kevin Layer
2013-02-27 15:37 ` Robert Pendell
2013-02-27 15:44 ` Eliot Moss
2013-02-27 15:50 ` Kevin Layer
2013-02-27 16:08 ` Eliot Moss
2013-02-27 16:20 ` Kevin Layer
2013-02-27 17:11 ` K Stahl
2013-02-27 18:07 ` Kevin Layer
2013-02-27 22:19 ` Kevin Layer
2013-02-27 23:14 ` Kevin Layer
2013-02-27 17:55 ` Jon TURNEY
2013-02-27 17:59 ` Kevin Layer
2013-02-27 19:50 ` Andrey Repin
2013-02-27 20:09 ` Christopher Faylor
2013-02-27 20:15 ` Kevin Layer
2013-02-27 21:17 ` Earnie Boyd
2013-02-27 22:16 ` Kevin Layer [this message]
2013-02-28 13:24 ` Earnie Boyd
2013-02-28 14:28 ` Kevin Layer
2013-03-01 14:11 ` Earnie Boyd
2013-03-01 15:49 ` Kevin Layer
2013-03-01 16:13 ` Chris J. Breisch
2013-03-01 17:35 ` Andrey Repin
2013-02-27 22:45 Kevin Layer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28423.1362003402@relay.known.net \
--to=layer@known.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).