From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200404210829.i3L8TXI10302@zamenhof.cs.utwente.nl> 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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10298.1082536173.1@zamenhof.cs.utwente.nl> Date: Wed, 21 Apr 2004 10:29:33 +0200 Topicbox-Message-UUID: 65958464-eacd-11e9-9e20-41e7f4b1d025 > > 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.