From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29386 invoked from network); 30 Oct 2008 22:16:45 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 30 Oct 2008 22:16:45 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 35791 invoked from network); 30 Oct 2008 22:16:40 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 30 Oct 2008 22:16:40 -0000 Received: (qmail 15718 invoked by alias); 30 Oct 2008 22:16:33 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 25977 Received: (qmail 15700 invoked from network); 30 Oct 2008 22:16:31 -0000 Received: from bifrost.dotsrc.org (130.225.254.106) by sunsite.dk with SMTP; 30 Oct 2008 22:16:31 -0000 Received: from mtaout01-winn.ispmail.ntl.com (mtaout01-winn.ispmail.ntl.com [81.103.221.47]) by bifrost.dotsrc.org (Postfix) with ESMTP id 43B3980524C0 for ; Thu, 30 Oct 2008 23:16:27 +0100 (CET) Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20081030221627.MIS21227.mtaout01-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com> for ; Thu, 30 Oct 2008 22:16:27 +0000 Received: from pws-pc.ntlworld.com ([81.107.43.40]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20081030221627.WAQF19264.aamtaout01-winn.ispmail.ntl.com@pws-pc.ntlworld.com> for ; Thu, 30 Oct 2008 22:16:27 +0000 Received: from pws-pc (pws-pc [127.0.0.1]) by pws-pc.ntlworld.com (8.14.2/8.14.2) with ESMTP id m9UMGGFX012035 for ; Thu, 30 Oct 2008 22:16:16 GMT Message-Id: <200810302216.m9UMGGFX012035@pws-pc.ntlworld.com> From: Peter Stephenson To: Zsh workers Subject: Re: another bug: zsh_directory_name In-Reply-To: Message from Oliver Kiddle of "Thu, 30 Oct 2008 22:20:54 +0100." <20324.1225401654@thecus> Date: Thu, 30 Oct 2008 22:16:16 +0000 X-Cloudmark-Analysis: v=1.0 c=1 a=Rv8XxGmo984A:10 a=NLZqzBF-AAAA:8 a=nNJLZhjoaaoVzK12jRsA:9 a=7aE-Ms28sJFd15FE4nIA:7 a=afO3xZ2tYVyRqj-V_CG2TXWZTQIA:4 a=_dQi-Dcv4p4A:10 a=p2VOdof_XD0A:10 X-Virus-Scanned: ClamAV 0.92.1/8544/Thu Oct 30 19:59:19 2008 on bifrost X-Virus-Status: Clean Oliver Kiddle wrote: > Out of interest what are people using this for. It seems like a nice > idea, but I've yet to think of an actual use that can't be done with a > normal named directory. Transformations on the current $PWD seem to be > one logical option - ${PWD/src/include} for instance. Or an easier syntax > for (../)# I'm using it for simplified hierarchies. ~[p] means my normal Perforce client, ~[p1] my alternative one, so ~[p:u] is /home/pws/perforce/uwb/main/fw/src while ~[p1:u] is /home/pws/perforcel1/uwb/main/fw/src, and so on. In other words, I can replace multiple chunks in the directory path very briefly; I could only do that with static names by naming every possible combination. See my previous post for how I'm doing completion on these. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/