From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <20140611195245.B8F5AB827@mail.bitblocks.com>
References: <20140611195245.B8F5AB827@mail.bitblocks.com>
Date: Wed, 11 Jun 2014 22:27:34 +0100
Message-ID: <CAH+xwdDgnhJ8D__2Jh3gfFqgA+EtZrR7WidS1aOzW-JycU3gdQ@mail.gmail.com>
From: Robert Raschke <rtrlists@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=047d7b41c0ccd84db604fb961c8d
Subject: Re: [9fans] long paths in acme tags
Topicbox-Message-UUID: f9ca8a3e-ead8-11e9-9d60-3106f5b1d025

--047d7b41c0ccd84db604fb961c8d
Content-Type: text/plain; charset=UTF-8

Whenever they are available, I use symlinks for "shortening" paths for
Acme. This is so far the only good use I've found for them ;-)

Robby
 On Jun 11, 2014 8:54 PM, "Bakul Shah" <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.
>
>

--047d7b41c0ccd84db604fb961c8d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Whenever they are available, I use symlinks for &quot;shortening&quot; p=
aths for Acme. This is so far the only good use I&#39;ve found for them ;-)=
</p>
<p>Robby<br>
</p>
<div class=3D"gmail_quote">On Jun 11, 2014 8:54 PM, &quot;Bakul Shah&quot; =
&lt;<a href=3D"mailto:bakul@bitblocks.com">bakul@bitblocks.com</a>&gt; wrot=
e:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you are editing multiple file within the same directory<br>
with a very long path, the long dir paths is what takes up<br>
most of the tag. One idea (borrowed from zsh) is to assign a<br>
long path to a variable and then just show the variable<br>
instead. Thus for example, given long paths like these:<br>
<br>
=C2=A0 =C2=A0 /a/very/very/very/very/very/very/very/very/very/long/path/to/=
a/file1<br>
=C2=A0 =C2=A0 /a/very/very/very/very/very/very/very/very/very/long/path/to/=
a/file2<br>
<br>
If one can define a variable in acme<br>
=C2=A0 =C2=A0 foo=3D/a/very/very/very/very/very/very/very/very/very/long/pa=
th/to/a<br>
<br>
&amp; if the acme tags show<br>
=C2=A0 =C2=A0 $foo/file1<br>
=C2=A0 =C2=A0 $foo/file2<br>
it would be much nicer.<br>
<br>
Has anyone considered doing this or is there a better idea? =C2=A0I<br>
suppose on plan9 one can use bind for this but on p9p things<br>
get considerably clunkier (9p, fuse...) when a variable can do<br>
the job more simply.<br>
<br>
</blockquote></div>

--047d7b41c0ccd84db604fb961c8d--