From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] Codebase navigation and using tags files in acme
Date: Fri, 20 Aug 2021 16:08:40 -0700 [thread overview]
Message-ID: <917939d480bd66878d0cb20ac175db16@9srv.net> (raw)
In-Reply-To: <CAHqDL_-4Znn=c36ymN48i-+CaQxXYs=U2Ym99kOUN1v_QhkqjQ@mail.gmail.com>
I did port Exuberant ctags several years ago when I was
dealing with a large body of unfamiliar code for a
project. Mine is here:
http://9p.io/sources/contrib/anothy/src/ctags/
It is a pretty straight-forward port, just adding an
output type suitable for acme (file:n). About a year
ago (I think?) someone told me that they did an
updated port, but I can't find the reference quickly.
Personally, I find ctags (and similar tools) useful
only in extreme circumstances, and otherwise rely only
on acme's built-in matching and a few scripts similar
to what's been posted here.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf8ceac12df9da674-M32237c6cd7f205230d8b175a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-08-20 23:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 20:22 Ben Hancock
2021-08-18 6:52 ` sirjofri
2021-08-18 9:12 ` Richard Miller
2021-08-18 9:17 ` Gabriel Diaz Lopez de la Llave via 9fans
2021-08-18 9:25 ` Rob Pike
2021-08-18 16:01 ` Ben Hancock
2021-08-19 11:44 ` Maurizio Boriani
2021-08-19 11:49 ` Gorka Guardiola
2021-08-19 18:59 ` unobe
2021-08-19 19:00 ` unobe
2021-08-19 20:41 ` Rob Pike
2021-08-18 9:13 ` Nick Owens
2021-08-18 9:26 ` Ole-Hjalmar Kristensen
2021-08-19 3:51 ` 6o205zd02
2021-08-19 7:29 ` igor
2021-08-20 10:55 ` Ole-Hjalmar Kristensen
2021-08-20 23:08 ` a [this message]
2021-08-20 23:31 ` Steve Simon
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=917939d480bd66878d0cb20ac175db16@9srv.net \
--to=a@9srv.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).