From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-6405-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 17543 invoked from network); 1 Jun 1999 04:52:40 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 1 Jun 1999 04:52:40 -0000
Received: (qmail 25627 invoked by alias); 1 Jun 1999 04:52:33 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 6405
Received: (qmail 25620 invoked from network); 1 Jun 1999 04:52:32 -0000
Message-Id: <199906010452.AAA16501@ocalhost>
Content-Type: text/plain
MIME-Version: 1.0
X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff
From: Timothy J Luoma <tjlists@bigfoot.com>
Date: Tue,  1 Jun 1999 00:52:19 -0400
To: zsh-workers@sunsite.auc.dk
Subject: why bother with 'cd .' ?


This seemed to confuse my /bin/sh:


cd . && \
  CONFIG_FILES= CONFIG_HEADERS=./config.h ./config.status
/bin/sh: .: bad directory


(now I can't tell you why it confused /bin/sh, sometimes it seems to work  
and other times it gives that error)


could we have something like

if [ "$PWD" != "$SRC_DIR" ]

	cd $SRC_DIR
fi

(using whatever the proper variables are)

It just seems like an unnecessary step which for some reason can cause confusion

TjL