From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] p9 mice From: Fco.J.Ballesteros In-Reply-To: <200404210829.i3L8TXI10302@zamenhof.cs.utwente.nl> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-bstrguflqdspevovryraswvlht" Date: Wed, 21 Apr 2004 10:44:35 +0200 Topicbox-Message-UUID: 659afbce-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-bstrguflqdspevovryraswvlht Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I thought about giving replacement strings to avoid those long paths, but in a controlled way. Eg, like saying /a/long/path/imported/from/somewhere/else -> /alongpath and then seing aroung /alongpath instead of the other and making wily make the change. Regarding acme, it doesn't bother me much as to like to change the current behaviour. --upas-bstrguflqdspevovryraswvlht Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Wed Apr 21 10:30:57 MDT 2004 Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id D17DF19AFD; Wed, 21 Apr 2004 04:30:47 -0400 (EDT) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id DE71019AFD; Wed, 21 Apr 2004 04:30:27 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001) id BD37219ACA; Wed, 21 Apr 2004 04:29:38 -0400 (EDT) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 74345199DB for <9fans@cse.psu.edu>; Wed, 21 Apr 2004 04:29:36 -0400 (EDT) Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.12.10/8.12.9) with ESMTP id i3L8TXCi000106 for <9fans@cse.psu.edu>; Wed, 21 Apr 2004 10:29:33 +0200 (MET DST) Received: from zamenhof.cs.utwente.nl (zamenhof [130.89.13.77]) by zeus.cs.utwente.nl (8.12.10/8.12.10) with ESMTP id i3L8TX8H021235 for <9fans@cse.psu.edu>; Wed, 21 Apr 2004 10:29:33 +0200 (MEST) Received: from localhost (belinfan@localhost) by zamenhof.cs.utwente.nl (8.11.7p1+Sun/8.10.2) with SMTP id i3L8TXI10302 for <9fans@cse.psu.edu>; Wed, 21 Apr 2004 10:29:33 +0200 (MEST) Message-Id: <200404210829.i3L8TXI10302@zamenhof.cs.utwente.nl> X-Authentication-Warning: zamenhof.cs.utwente.nl: belinfan@localhost didn't use HELO protocol To: 9fans@cse.psu.edu Subject: Re: [9fans] p9 mice In-reply-to: Your message of "Wed, 21 Apr 2004 09:53:25 +0200." References: From: Axel Belinfante X-Organisation: University of Twente, Department of Computer Science, Formal Methods and Tools Group, PO Box 217, NL-7500 AE Enschede, The Netherlands X-Phone: +31 53 4893774 X-Telefax: +31 53 4893247 X-Face: 3YGZY^_!}k]>-k'9$LK?8GXbi?vs=2v*ut,/8z,z!(QNBk_>~:~"MJ_%i`sLLqGN,DGbkT@ N\jhX/jNLTz2hO_R"*RF(%bRvk+M,iU7SvVJtC*\B6Ud<7~`MGMp7rCI6LVp=%k=HE?-UCV?[p\$R? mI\n2/!#3/wZZsa[m7d;PKWiuH6'~ X-Virus-Scanned: clamd / ClamAV version 0.67, clamav-milter version 0.66n Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Wed, 21 Apr 2004 10:29:33 +0200 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Level: > > I also liked the possibility to button3 on e.g. $PLAN9/src . > > This is different. (although we might have problems to plumb messages > that already include $). (to state the obvous: I like it because scripts, readmes and similar text may contain references just like that.) I also have handful of variables for 'deep' subdirs I often visit. > However, having wily on its own replace > /x/y/z with $A/z is something that bothers me. (I did also the trick of > undef PWD, but then other shells defined other variables, ... ugh). I see your point. I only use a few shells, and after a while you know what to undef. The number of accidental replacements were in my case minimal. Would you be happy if you could explicitly specify the replacements? (or would that only increase complexity?) Maybe my problem is that my dir/file names are longer than x, y or z, (rooted path to home dir already takes 18 characters) So, for me, the replacements save screen (tag) space. Also, for the often-visited subdirs, the path represented by $A is of no particular interest to me, the information is in the file/dir name to the right of the $A/ (the z in your example). So, $A instead of /this/long/path/to/where/I/start/working just gives me space I can use as scratch space without having to scroll in the tag. Axel. --upas-bstrguflqdspevovryraswvlht--