[1439] in SIPB_Linux_Development
Re: csh.cshrc
daemon@ATHENA.MIT.EDU (derekt@MIT.EDU)
Thu Sep 19 15:51:16 1996
From: derekt@MIT.EDU
To: Derek Atkins <warlord@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: Your message of "Thu, 19 Sep 1996 13:45:35 EDT."
<9609191745.AA28357@bart-savagewood.MIT.EDU>
Date: Thu, 19 Sep 1996 15:50:25 EDT
why did I install that one?
it was there.
I don't know really.
Somebody in my house thought I'd be better off going that way,
although I kept asking him what the differences were between 3.0.3 and
3.0.4, and he had no real answer, besides, "It's newer."
which some would see as a disadvantage.
sorry if I'm wasting your time by making you reply about known bugs
and what not, but I figured you might be interested in another
person's input. then again, maybe not....
basically, my point is that you really don't have to reply to this if
you don't want to. I went with an unsupported install, and you
shouldn't have to support it. I sent mail for your benefit, and if it
isn't for your benefit, delete it, and I'll go away.
---
> /etc/csh.cshrc out of the way, is wrong. A better fix, for now, is to
> "touch /etc/profile.d/foo.csh", which will cause the symptoms to go
> away.
okay, I'll make the /etc/profile.d/dummy.csh file.
but, the first way that I tried to get around the not sourcing
$HOME/.cshrc, was to put
source $HOME/.cshrc
into csh.cshrc.
and then echos in the .cshrc, .cshrc.mine, and $initdir/.cshrc were
echoed, but no changes of substance were made.
as noted in the other letter, things like if ($?prompt) could make a
difference, but I think there were more problems that that.
and for the record, putting "csh $HOME/.cshrc" in a csh.cshrc file is
a bad idea. :-)
---
> > added a "set host = ..." in the initdir's cshrc, and
> > added a if (! $?NOCALLS) set path = (/bin/athena)
> > to avoid attach errors.
>
> You shouldn't have to do this, if you fix /etc/csh.cshrc. What
> "attach" errors do you get?
some people put /bin/athena things in their .environment, such as
'attach' and 'aklog'.
If the .environment is sourced before /bin/athena is in their path,
file not found errors occur.
The end of the $initdir/cshrc file seems to clobber any input path,
anyway, so it seemed okay for me to clobber it earlier on, and then
have the temporary /bin/athena path get clobbered at the end of the
cshrc.
---
oh, and it appears that tcsh is only willing to complete if it can
find a single match; it won't tell you all of the possible matches.
but I've found this true on other linux boxes, as well.
---
oh, and about the libncurses 2.0, I forgot I added a hack to get
around that.
namely, ln -s libncurses1.9.9e libncurses2.0
perhaps not the most correct solution, but it's worked so far. :-)
later Derek,
Derek.
