From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Date: Fri,  4 Jun 2004 09:19:19 +0000
From: Bengt Kleberg <bengt.kleberg@ericsson.com>
Message-ID: <c9pcgl$ksf$1@newstree.wise.edt.ericsson.se>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
References: <4d30561ec4fd4a26b45150a2416c002a@9srv.net>,
	<855f2a51294c4e27df6f583286e23e28@vitanuova.com>
Subject: Re: [9fans] acme design
Topicbox-Message-UUID: 94c2df70-eacd-11e9-9e20-41e7f4b1d025

rog@vitanuova.com wrote:
> i been thinking that one way to make the filenames less obtrusive in
> acme would be to allow grouping of windows with a common path prefix.
> 
> i quite often find myself working in, say
> /n/dump/2004/0529/usr/inferno/appl/cmd/scheduler/...  and that really
> doesn't give much space for tag commands.
> 
> i could imagine some kind of directory-tagged super-window in acme
> that contained other windows.

does acme use existing environment variables, like wily does?

from the idioms webpage (http://www.cs.yorku.ca/~oz/wily/idioms.html):

Short-cut Environment Variables
Set environment variables to make window labels shorter and easier to 
type, e.g.

	h = $HOME
	wilysrc = $h/src/wily/wily
	wilybin = $h/obj/$cputype/wily/wily


bengt