From: "Masterson, Dave" <dmasters@rational.com>
To: 'DJ Delorie' <dj@delorie.com>
Cc: cygwin@sources.redhat.com
Subject: RE: /etc/profile in BASH
Date: Thu, 28 Sep 2000 14:18:00 -0000 [thread overview]
Message-ID: <C322F78942E6D311AF8800D0B73C4FD8830D31@CUPEX3.rational.com> (raw)
Example? Why would it be? And if it is, wouldn't BASH use the new value to
determine where to get ~/.profile and ~/.bashrc? (I should test that,
but...)
Point is that doing this in /etc/profile subverts --noprofile and --norc
options in BASH.
-----Original Message-----
From: DJ Delorie [ mailto:dj@delorie.com ]
Sent: Thursday, September 28, 2000 1:04 PM
To: dmasters@Rational.Com
Cc: cygwin@sources.redhat.com
Subject: Re: /etc/profile in BASH
> As described in the BASH MAN page, it would seem that BASH does this
already
> after reading /etc/profile. Is this required because of the
implementation
> of Cygwin on MS-Windows?
It's in case $HOME is set or changed by /etc/profile.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-09-28 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-28 14:18 Masterson, Dave [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 12:50 Earnie Boyd
2000-09-29 12:43 Masterson, Dave
2000-09-29 12:31 Earnie Boyd
2000-09-29 12:05 Earnie Boyd
2000-09-29 11:56 Masterson, Dave
2000-09-29 11:36 Earnie Boyd
2000-09-29 11:31 Masterson, Dave
2000-09-29 11:25 Earnie Boyd
2000-09-29 11:42 ` Erik Nolte
2000-09-29 9:42 Masterson, Dave
2000-09-29 5:04 Earnie Boyd
2000-09-28 11:38 Masterson, Dave
2000-09-28 13:04 ` DJ Delorie
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=C322F78942E6D311AF8800D0B73C4FD8830D31@CUPEX3.rational.com \
--to=dmasters@rational.com \
--cc=cygwin@sources.redhat.com \
--cc=dj@delorie.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).