From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (exuberant) ctags and ConTeXt
Date: Mon, 19 Dec 2011 00:13:53 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.02.1112190010010.10802@nqv-gnoyrg.tngrjnl.2jver.arg> (raw)
In-Reply-To: <CAHJRaA4Z1bbwELDN9+oqtbW1a_R5b1zUY2P9q_67hh9Y8i=VDw@mail.gmail.com>
On Sun, 18 Dec 2011, Chris Lott wrote:
> Does anyone have a current working configuration for exuberant-ctags
> (I'm using it in vim) to work with ConTeXt? The ctags FAQ shows how to
> do it for LaTeX with regexes in a configuration file...
> http://vim-taglist.sourceforge.net/extend.html
>
> I can hack away at those, but in case anyone has done this already I
> wouldn't have to reinvent that particular wheel.
I had (about 4 years ago) written a ctags module that redefined a low
level reference macro so that a ctags file was automatically written when
you compiled your document.
If I were to write it again, I will just write a mtx-ctags.lua file that
will read the filename.tuc file (all the info is there as a lua table) and
write it to a ctags file in the right format. You can then set the ctags
program in vim to `mtxrun --script ctags filename.tex`
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-12-19 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 23:08 Chris Lott
2011-12-19 5:13 ` Aditya Mahajan [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=alpine.LNX.2.02.1112190010010.10802@nqv-gnoyrg.tngrjnl.2jver.arg \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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).