Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!pyramid!prls!mips!dce
From: dce@mips.UUCP (David Elliott)
Newsgroups: comp.unix.questions
Subject: Re: Korn Shell
Message-ID: <209@quacky.mips.UUCP>
Date: Wed, 18-Mar-87 12:35:18 EST
Article-I.D.: quacky.209
Posted: Wed Mar 18 12:35:18 1987
Date-Received: Fri, 20-Mar-87 02:08:14 EST
References: <580@csun.UUCP> <5680@brl-smoke.ARPA> <2201@ptsfa.UUCP> <730@hoqax.UUCP> <15224@sun.uucp>
Reply-To: dce@quacky.UUCP (David Elliott)
Organization: MIPS Computer Systems, Sunnyvale, CA
Lines: 28
Keywords: Korn shell ksh aliases parameters

In article <15224@sun.uucp> guy@sun.UUCP (Guy Harris) writes:
>>Why can't aliases and functions be exported like shell variables?
>
>[ good points about problems of distinguishing aliases and functions
>  and about copying so much stuff ]

One point that hasn't been mentioned is how shell scripts would be
affected by having these items exported.

I've seen a number of csh scripts whose first line is either

	#

or

	#!/bin/csh

This means that it could use my aliases (except that I don't set
aliases for non-interactive shells), my paths, and other variables.

At least csh has worked this way from the start, so people that
don't write proper csh scripts get what they deserve. I wouldn't
particularly like it if all of my shell scripts became broken
just because aliases and functions all of a sudden got exported.
-- 
			David Elliott

UUCP: 	{decvax,ucbvax,ihnp4}!decwrl!mips!dce, DDD:  	408-720-1700