From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-2873-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 1856 invoked from network); 13 Jan 2000 09:32:55 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 13 Jan 2000 09:32:55 -0000
Received: (qmail 22389 invoked by alias); 13 Jan 2000 09:32:42 -0000
Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 2873
Received: (qmail 22382 invoked from network); 13 Jan 2000 09:32:42 -0000
Subject: Re: remote function problems.
In-Reply-To: <000001bf5da2$557cca70$21c9ca95@mow.siemens.ru> from Andrej Borsenkow
 at "Jan 13, 2000 11:43:58 am"
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Date: Thu, 13 Jan 2000 09:32:36 +0000 (GMT)
CC: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>, 
 zsh-users@sunsite.auc.dk
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <E128gcP-00015w-00@crucigera.fysh.org>
From: Zefram <zefram@fysh.org>

Andrej Borsenkow wrote:
>We already discussed it. IMHO it is bad idea to put this in zshenv. This will be
>executed for every shell, including zsh scripts, and not ony slows it down but,
>what's worse, function defintions may clash with external commands; it may
>redefine some commands script relies upon; etc ...

That's why zsh scripts start "#!.../zsh -f".  zshenv is the right place
to define functions.

-zefram