9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] long paths in acme tags
Date: Wed, 11 Jun 2014 14:23:32 -0700	[thread overview]
Message-ID: <20140611212332.DF260B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 11 Jun 2014 22:33:07 +0200." <CAEAzY3_HEKR7ZtPP=GYqCjRk5UqBeT_is0_XUk_rtiGz4gzabg@mail.gmail.com>

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.



  parent reply	other threads:[~2014-06-11 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 19:52 Bakul Shah
2014-06-11 20:02 ` erik quanstrom
2014-06-11 20:33 ` Aram Hăvărneanu
2014-06-11 20:37   ` erik quanstrom
2014-06-11 21:23   ` Bakul Shah [this message]
2014-06-11 21:27 ` Robert Raschke
2014-06-11 21:32   ` Bakul Shah
2014-06-11 21:56     ` erik quanstrom
2014-06-11 22:23     ` Nicolas Bercher
2014-06-12 17:44       ` Bakul Shah
2014-06-11 20:11 sl
2014-06-11 20:21 ` erik quanstrom
2014-06-11 20:31 sl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140611212332.DF260B827@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).