From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 11 Jun 2014 16:02:49 -0400
To: 9fans@9fans.net
Message-ID: <9500173bc2825402764e6f739dbf3c64@brasstown.quanstro.net>
In-Reply-To: <20140611195245.B8F5AB827@mail.bitblocks.com>
References: <20140611195245.B8F5AB827@mail.bitblocks.com>
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: f989425e-ead8-11e9-9d60-3106f5b1d025

On Wed Jun 11 15:56:59 EDT 2014, bakul@bitblocks.com wrote:
> If you are editing multiple file within the same directory
> with a very long path, the long dir paths is what takes up
> most of the tag. One idea (borrowed from zsh) is to assign a
> long path to a variable and then just show the variable
> instead. Thus for example, given long paths like these:
>
>     /a/very/very/very/very/very/very/very/very/very/long/path/to/a/file1
>     /a/very/very/very/very/very/very/very/very/very/long/path/to/a/file2
>
> 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.

- erik