From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 11 Jun 2014 16:21:42 -0400
To: 9fans@9fans.net
Message-ID: <794d8ec213894301e84bfcc6be2a4f2a@brasstown.quanstro.net>
In-Reply-To: <f1463105dfff5c71c4eee1ab63ed0d4d@pi.att>
References: <f1463105dfff5c71c4eee1ab63ed0d4d@pi.att>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] long paths in acme tags
Topicbox-Message-UUID: f993637e-ead8-11e9-9d60-3106f5b1d025

On Wed Jun 11 16:14:54 EDT 2014, sl@9front.org wrote:
> >> If one can define a variable in acme
> >>     foo=/a/very/very/very/very/very/very/very/very/very/long/path/to/a
> >>
> >> & if the acme tags show
> >>     $foo/file1
> >>     $foo/file2
> >> it would be much nicer.
> >>
> >> Has anyone considered doing this or is there a better idea?  I
> >> suppose on plan9 one can use bind for this but on p9p things
> >> get considerably clunkier (9p, fuse...) when a variable can do
> >> the job more simply.
> >
> > this was done in wily in the mid 90s, complete with an algorithm
> > to find the shortest representation.
>
> What was the result? In which distribution is it available? How is
> it used?

wily was a stand-alone unix program.  iirc it relied on the frame library
port from plan 9.

it worked, but the problem was that environment variables are not
understood by the kernel.

google "wily text editor".

- erik