Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uwm.edu!linac!att!cbnews!lvc
From: lvc@cbnews.att.com (lawrence.v.cipriani)
Newsgroups: comp.unix.shell
Subject: Re: ksh - how do you keep aliases permanent?
Message-ID: <1991Mar11.041751.18032@cbnews.att.com>
Date: 11 Mar 91 04:17:51 GMT
References: <57993@mcdchg.chg.mcd.mot.com> <7365@mentor.cc.purdue.edu> <544@genco.bungi.com>
Organization: Ideology Busters, Inc.
Lines: 16

In article <544@genco.bungi.com> rad@genco.bungi.com (Bob Daniel) writes:
>When defining aliases, is there a way to keep them permanent as they are defined
>rather than inserting them directly into .profile?  If I have to, I'll write
>something that makes aliases and stores them in a file that is launched by
>.profile at login but would like to know if it can be done before spending 
>time on that routine.

I guess I'm not entirely certain what you mean by "keep them permanent."
If you want those aliases and functions accessible to sub-shells try this:
export and define a variable called ENV in .profile; $ENV is the name of
an environment file ksh will automatically "dot" after .profile when you
login.  You do not have to say . $ENV in your .profile, it is redundant
[at login].
-- 
Larry Cipriani, att!cbvox!lvc or lvc@cbvox.att.com
"Fight fire with fire, I always say" -- Bugs Bunny