From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] long paths in acme tags
Date: Wed, 11 Jun 2014 16:02:49 -0400 [thread overview]
Message-ID: <9500173bc2825402764e6f739dbf3c64@brasstown.quanstro.net> (raw)
In-Reply-To: <20140611195245.B8F5AB827@mail.bitblocks.com>
On Wed Jun 11 15:56:59 EDT 2014, bakul@bitblocks.com wrote:
> If you are editing multiple file within the same directory
> with a very long path, the long dir paths is what takes up
> most of the tag. One idea (borrowed from zsh) is to assign a
> long path to a variable and then just show the variable
> instead. Thus for example, given long paths like these:
>
> /a/very/very/very/very/very/very/very/very/very/long/path/to/a/file1
> /a/very/very/very/very/very/very/very/very/very/long/path/to/a/file2
>
> 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.
- erik
next prev parent reply other threads:[~2014-06-11 20:02 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 [this message]
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
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=9500173bc2825402764e6f739dbf3c64@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).