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: From: Robert Raschke 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" 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

Whenever they are available, I use symlinks for "shortening" p= aths 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> wrot= e:
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:

=C2=A0 =C2=A0 /a/very/very/very/very/very/very/very/very/very/long/path/to/= a/file1
=C2=A0 =C2=A0 /a/very/very/very/very/very/very/very/very/very/long/path/to/= a/file2

If one can define a variable in acme
=C2=A0 =C2=A0 foo=3D/a/very/very/very/very/very/very/very/very/very/long/pa= th/to/a

& if the acme tags show
=C2=A0 =C2=A0 $foo/file1
=C2=A0 =C2=A0 $foo/file2
it would be much nicer.

Has anyone considered doing this or is there a better idea? =C2=A0I
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--