From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26306 invoked from network); 4 Aug 1998 14:26:49 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 4 Aug 1998 14:26:49 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id KAA06786; Tue, 4 Aug 1998 10:19:08 -0400 (EDT) Resent-Date: Tue, 4 Aug 1998 10:19:08 -0400 (EDT) Date: Tue, 4 Aug 1998 16:21:23 +0200 (MET DST) From: "C. v. Stuckrad" X-Sender: stucki@petzval Reply-To: "C. v. Stuckrad" To: Zsh workers list Subject: PATH handling broken in zsh 3.1.4 Message-ID: X-TestHeaderA: Written by C. v. Stuckrad; FB. Mathematik; EDV X-TestHeaderB: FU-Berlin; Arnimallee 2-6; 14195 Berlin; GERMANY Priority: normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Message-ID: <"dGMX5.0.zf1.RXnnr"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4260 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Hi! I just noticed, that zsh *ignores* empty fields in 'path' (created via 'PATH') instead of implying a 'dot'. 'csh' does: setenv PATH bla: echo $path bla . '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 bla bla ^^ there _was_ the 'implied dot' :-) Your's Stucki Christoph von Stuckrad * * | talk to | \ Freie Universitaet Berlin |/_* | nickname | ...!unido!fub!leibniz!stucki| Fachbereich Mathematik, EDV |\ * | 'stucki' | Tel:+49 30 838-75459 | Arnimallee 2-6/14195 Berlin * * | on IRC | Fax:+49 30 838-75454 /