From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] long paths in acme tags
Date: Wed, 11 Jun 2014 16:21:42 -0400 [thread overview]
Message-ID: <794d8ec213894301e84bfcc6be2a4f2a@brasstown.quanstro.net> (raw)
In-Reply-To: <f1463105dfff5c71c4eee1ab63ed0d4d@pi.att>
On Wed Jun 11 16:14:54 EDT 2014, sl@9front.org wrote:
> >> 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.
> >
> > this was done in wily in the mid 90s, complete with an algorithm
> > to find the shortest representation.
>
> What was the result? In which distribution is it available? How is
> it used?
wily was a stand-alone unix program. iirc it relied on the frame library
port from plan 9.
it worked, but the problem was that environment variables are not
understood by the kernel.
google "wily text editor".
- erik
next prev parent reply other threads:[~2014-06-11 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 20:11 sl
2014-06-11 20:21 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-11 20:31 sl
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
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
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=794d8ec213894301e84bfcc6be2a4f2a@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).