From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28975 invoked from network); 4 Aug 1998 15:25:55 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 4 Aug 1998 15:25:55 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id LAA07967; Tue, 4 Aug 1998 11:18:25 -0400 (EDT) Resent-Date: Tue, 4 Aug 1998 11:18:25 -0400 (EDT) Message-Id: <199808041520.QAA25207@diamond.tao.co.uk> Subject: Re: PATH handling broken in zsh 3.1.4 To: stucki@math.fu-berlin.de Date: Tue, 4 Aug 1998 16:20:00 +0100 (BST) From: "Zefram" Cc: zsh-workers@math.gatech.edu In-Reply-To: from "C. v. Stuckrad" at Aug 4, 98 04:21:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"IU0_m.0.Qy1.1Ponr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4261 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu C. v. Stuckrad wrote: >I just noticed, that zsh *ignores* empty fields in >'path' (created via 'PATH') instead of implying a 'dot'. No it doesn't. It treats the entries as meaning the current directory. >'csh' does: setenv PATH bla: > echo $path > bla . zsh doesn't actually translate "" -> "." when setting the path, however. >'zsh' ignores the trailing colon, and even drops colons when using >'vared PATH' on a Path containig empty fields. Like: >'export PATH=bla::bla'; vared path vared on an array variable is a lossy process. Try "vared PATH" instead. -zefram