From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] long paths in acme tags
Date: Wed, 11 Jun 2014 16:37:44 -0400 [thread overview]
Message-ID: <66ca84ae9a8683c5a646ec103ea1e660@brasstown.quanstro.net> (raw)
In-Reply-To: <CAEAzY3_HEKR7ZtPP=GYqCjRk5UqBeT_is0_XUk_rtiGz4gzabg@mail.gmail.com>
On Wed Jun 11 16:34:51 EDT 2014, 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.
both of these issues can be sorted. there's no reason the cut text
or plumb'd text need equal the displayed text. but one would need
to be very careful about it.
- erik
next prev parent reply other threads:[~2014-06-11 20:37 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 [this message]
2014-06-11 21:23 ` Bakul Shah
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=66ca84ae9a8683c5a646ec103ea1e660@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).