Subject: Re: CVS commit: basesrc/bin/ksh
To: None <firstname.lastname@example.org>
From: Joerg Klemenz <email@example.com>
Date: 10/01/2002 17:02:34
Jaromir Dolecek wrote:
> Joerg Klemenz wrote:
> > If you login w/ ksh and run "csh" it executes /etc/csh.cshrc and ~/.cshrc.
> > That makes it very easy for the user: No need for workarounds and tons
> > of "if [..", just put everything in .cshrc
> > Makes a lot of sense to me
> "Me too". I suffered to the strange way (pd)ksh needs to be setup
> couple of times, and I'd strongly preferred if I wouldn't be required
> to do the ENV setup etc. Shouldn't be too hard to implement ...
An extension like this could be implemented totally transparent.
ksh could look for [/etc/|~/.] kshenv, kprofile, kshrc and ignore
profile and ENV.
If kprofile does not exist ksh would load the standard sh files. That
way existing users wouldn't even notice it, and no changes would be
required in greg's scripts :)
Just make sure not to duplicate csh's design flaws and *not* load
kshrc for non-interactive shells (see other mail).