[26148] in Athena Bugs

home help back first fref pref prev next nref lref last post

Re: $initdir scripts

daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Oct 22 14:40:48 2004

From: Greg Hudson <ghudson@mit.edu>
To: Jacob Morzinski <jmorzins@mit.edu>
In-Reply-To: <1098469722.13060.174.camel@egyptian-gods.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1098470379.13060.181.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0
Date: Fri, 22 Oct 2004 14:39:39 -0400
cc: bugs@mit.edu
Errors-To: bugs-bounces@mit.edu

On Fri, 2004-10-22 at 14:28, Greg Hudson wrote:
> > Fixed by changing ${ENV_SET:+set} to just ${ENV_SET+set} .
> 
> Hm.  I hope the tcsh dotfiles set up all the environment stuff expected
> by the bash ones, then.  But I can see the problems with the current
> approach.

Hm.  The use of ${ENV_SET:+set} is deliberate, as explained in the
following CVS log message:

revision 1.15
date: 2000/10/14 17:33:39;  author: ghudson;  state: Exp;  lines: +2 -2
Kludge: The standard cshrc gets run when bash users do an X login,
because they get a csh xsession.  So the first time we run, ENV_SET is
often already set, to a blank value.  Because we want to run .bashrc,
do the environment setup is ENV_SET is empty.  (We set it to 't', so
we still won't run it twice.)

I think I meant to say .bash_environment, not .bashrc, in the
second-to-last sentence.

I can see how the current behavior is harmful to tcsh users who run
bash, but your proposed solution would be a regression for bash users. 
I'll have to think about this problem.  I'll submit your other fixes in
the meantime.


home help back first fref pref prev next nref lref last post