From mboxrd@z Thu Jan  1 00:00:00 1970
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-reply-to: Your message of "Wed, 11 Jun 2014 22:33:07 +0200."
	<CAEAzY3_HEKR7ZtPP=GYqCjRk5UqBeT_is0_XUk_rtiGz4gzabg@mail.gmail.com>
References: <20140611195245.B8F5AB827@mail.bitblocks.com>
	<CAEAzY3_HEKR7ZtPP=GYqCjRk5UqBeT_is0_XUk_rtiGz4gzabg@mail.gmail.com>
Date: Wed, 11 Jun 2014 14:23:32 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20140611212332.DF260B827@mail.bitblocks.com>
Subject: Re: [9fans] long paths in acme tags
Topicbox-Message-UUID: f9bd2d30-ead8-11e9-9d60-3106f5b1d025

On Wed, 11 Jun 2014 22:33:07 +0200 =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= <aram.h@mgk.ro> wrote:
> > & if the acme tags show
> >     $foo/file1
> >     $foo/file2
> > it would be much nicer.
>
> Real paths are plumbable and copyable, variable names are not. p9p
> acme (where this problem is more acute) has multiline tags.

Multiline tags don't help with the clutter. In any case I am
only talking about what is displayed in the tag.

I have never need to plumb the tag. Valid point about copying
but you can deal with that by defining similar variables in rc.

Thanks Erik, I will take a look at wily code.