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:32:07 -0700 [thread overview]
Message-ID: <20140611213207.814DDB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 11 Jun 2014 22:27:34 BST." <CAH+xwdDgnhJ8D__2Jh3gfFqgA+EtZrR7WidS1aOzW-JycU3gdQ@mail.gmail.com>
On Wed, 11 Jun 2014 22:27:34 BST Robert Raschke <rtrlists@googlemail.com> wrote:
>
> 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 ;-)
Symlinks don't help in the tag as pwd finds the real path.
next prev parent reply other threads:[~2014-06-11 21:32 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
2014-06-11 21:27 ` Robert Raschke
2014-06-11 21:32 ` Bakul Shah [this message]
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=20140611213207.814DDB827@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).