From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12883 invoked from network); 14 Dec 2000 13:00:27 -0000 Received: from sunsite.dk (HELO sunsite.auc.dk) (130.225.51.30) by ns1.primenet.com.au with SMTP; 14 Dec 2000 13:00:27 -0000 Received: (qmail 11347 invoked by alias); 14 Dec 2000 13:00:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13272 Received: (qmail 11333 invoked from network); 14 Dec 2000 13:00:19 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: "Alexandre Duret-Lutz" Cc: Subject: RE: :r modifier Date: Thu, 14 Dec 2000 16:00:05 +0300 Message-ID: <000901c065cd$c7b6c940$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > > Bart> :Do we need to teach :h/:t about the leading-double-slash > Bart> convention for some networked file systems? > > I don't know, I never seen such file systems. May be, you have heard about one. It is called Windows and (sometimes) runs on x86 PC-compatible systems :-) I checked bash and it behaves the same as zsh. On Cygwin bash is just as ignorant about special Win32 names as zsh is. It does not mean we should follow the suite - but, at least, we are in good company as it stand now :)) -andrej