From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29326 invoked from network); 1 Mar 1999 14:27:41 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Mar 1999 14:27:41 -0000 Received: (qmail 3843 invoked by alias); 1 Mar 1999 14:27:07 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 5581 Received: (qmail 3836 invoked from network); 1 Mar 1999 14:27:04 -0000 From: "Andrej Borsenkow" To: "Sven Wischnowsky" , Subject: RE: PATCH: Re: pws-10 RE: zsh-3.1.5-pws-9: _path_files and symbolic links Date: Mon, 1 Mar 1999 17:26:14 +0300 Message-ID: <003f01be63ef$75f69360$21c9ca95@mowp.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2013.2901 In-Reply-To: <199903011303.OAA14813@beta.informatik.hu-berlin.de> > > The question is what one can find under `/u/'. If there is anything > matching `l/l/T' the behavior might be correct (since it can't expand > `u' to `usr' then). Nope. It is the problem of exact match. ``/u'' is matched _exactly_ and hence ``/usr'' is never even tried. I have no ``/SAM/u'', that's why ``/SAM/usr'' is matched. It does not matter, what follows: itsrm1% ls -F /u pub/ sni/ Now I ask myself if it's desirable. As my example shows, it could be at least unexpected :-) And note, that ``cd /u'' correctly lists ``/usr'' as possible match. /andrej