From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7165 invoked from network); 15 Feb 2001 07:51:50 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 15 Feb 2001 07:51:50 -0000 Received: (qmail 27153 invoked by alias); 15 Feb 2001 07:51:39 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13482 Received: (qmail 27141 invoked from network); 15 Feb 2001 07:51:38 -0000 From: "Bart Schaefer" Message-Id: <1010215075055.ZM9762@candle.brasslantern.com> Date: Thu, 15 Feb 2001 07:50:55 +0000 In-Reply-To: <000101c09717$fdef3c10$21c9ca95@mow.siemens.ru> Comments: In reply to "Andrej Borsenkow" "RE: PATCH: stop null path component segfaults in whence" (Feb 15, 9:24am) References: <000101c09717$fdef3c10$21c9ca95@mow.siemens.ru> X-Mailer: Z-Mail (5.0.0 30July97) To: Subject: Re: PATCH: stop null path component segfaults in whence MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 15, 9:24am, Andrej Borsenkow wrote: } Subject: RE: PATCH: stop null path component segfaults in whence } } Empty element in PATH traditionally means current directory. Is it now } different in zsh? No, it still results in an empty element of the $path array, which is still interpreted as the current directory. Or at least it worked that way in the build I just did, which unless I've broken something else should have this patch in it. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net