9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] ctags on plan 9 with acme-friendly tags
Date: Mon, 18 Feb 2008 14:43:10 -0500	[thread overview]
Message-ID: <509071940802181143s3bfbeddcx72d2bb1824305598@mail.gmail.com> (raw)
In-Reply-To: <948781140802180924g2b1f03acue9253dd9e8fff93a@mail.gmail.com>

Okay, /n/sources/contrib/anothy/rc/bin/looktag is useful, i think.
It'll take a list of tags as arguments, look for them in a tags file
(-f file, or tags in the local dir by default), and plumbs the results
correctly. It's intended so that if you put it in the tag of an acme
window, 1-click at an identifier, and 2-1 chord looktag, it'll do the
right thing.

It'll handle multiple tags and multiple occurrences correctly. If
multiple tags are in one file, you only get the last one (I suppose
one could Zerox the window for each occurence if the file's already
open; have at it). I believe it'll work properly with p9p, but have
not tested it (later tonight).

As an aside, it might be nice of Acme provided the path or file name
the supplied argument in a 2-1 chord came from in the environment
somewhere. I imagine it'd be useful more generally, but here it'd
allow sticking (a modified) 'looktag' in a Guide file or similar and
using that for every window, rather than typing it in every window's
tag.

I spent a few minutes looking at doing a Limbo tagger and decided it
wasn't worth it for me, but I'd be interested if anyone decides to
give it a go.
Anthony


      reply	other threads:[~2008-02-18 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17  5:34 Anthony Sorace
2008-02-17  5:45 ` ron minnich
2008-02-17  7:01 ` Steve Simon
2008-02-17 14:05   ` Anthony Sorace
2008-02-18  9:30     ` Fco. J. Ballesteros
2008-02-17 15:18   ` Eric Van Hensbergen
2008-02-22 10:02   ` Douglas A. Gwyn
2008-02-18 17:24 ` balaji
2008-02-18 19:43   ` Anthony Sorace [this message]

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=509071940802181143s3bfbeddcx72d2bb1824305598@mail.gmail.com \
    --to=anothy@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).