Universal Ctags Hacking GuideΒΆ
- Version:
Draft
- Authors:
Universal Ctags developers
- Web Page:
Universal Ctags (abbreviated as u-ctags) is a maintained implementation of
ctags
.
ctags
generates an index (or tag) file of language objects found in source
files for programming languages.
This index makes it easy for text editors and other tools to locate the indexed
items.
Exuberant Ctags (e-ctags) maintained by Darren Hiebert, the ancestor of Universal Ctags, improved traditional ctags with multi-language support, the ability for the user to define new languages searched by regular expressions (called optlib in Universal Ctags), and the ability to generate emacs-style TAGS files. But the activity of the project unfortunately stalled.
Universal Ctags has the objective of continuing the development of Exuberant Ctags. Reza Jelveh <reza.jelveh@gmail.com> initially created a personal fork of Exuberant Ctags on GitHub. As interest and participation grew, it was decided to move development to a dedicated project as Universal Ctags. The goal of this project is to maintain a common/unified working space where people interested in making ctags better can work together.
Some of the major features of Universal Ctags are:
greater number of supported languages
- better language support
new extended C/C++ language parser, etc.
fully extended optlib (a feature to define a new language parser from a command line)
interactive mode (experimental)
The primary documents of Universal Ctags are man pages. Users should first consult the ctags(1), and other man pages if necessary.
This guide, which also includes the man pages, is primarily for developers and provides additional information to the man pages, including experimental features.
This is a draft document. Proofreading and pull-requests are welcome!
- Building ctags
- Man pages
- ctags(1)
- ctags-json-output(5)
- tags(5)
- ctags-optlib(7)
- ctags-client-tools(7)
- ctags-incompatibilities(7)
- ctags-faq(7)
- ctags-lang-asm(7)
- ctags-lang-autoit(7)
- ctags-lang-automake(7)
- ctags-lang-c(7)
- ctags-lang-c++(7)
- ctags-lang-cuda(7)
- ctags-lang-elm(7)
- ctags-lang-emacslisp(7)
- ctags-lang-fortran(7)
- ctags-lang-gdscript(7)
- ctags-lang-i18nrubygem(7)
- ctags-lang-iPythonCell(7)
- ctags-lang-inko(7)
- ctags-lang-javascript(7)
- ctags-lang-julia(7)
- ctags-lang-kconfig(7)
- ctags-lang-ldscript(7)
- ctags-lang-lex(7)
- ctags-lang-lisp(7)
- ctags-lang-make(7)
- ctags-lang-markdown(7)
- ctags-lang-powershell(7)
- ctags-lang-python(7)
- ctags-lang-r(7)
- ctags-lang-rmarkdown(7)
- ctags-lang-sql(7)
- ctags-lang-systemtap(7)
- ctags-lang-tcl(7)
- ctags-lang-terraform(7)
- ctags-lang-verilog(7)
- ctags-lang-vim(7)
- readtags(1)
- Parsers
- Option files
- Output formats
- Running multiple parsers on an input file
- Interactive mode
- NEWS
- Extending ctags with Regex parser (optlib)
- Language definition flags
- Regular expression (regex) engine
- Perl-compatible regular expressions (PCRE2) engine
- Regex option argument flags
- Overriding the letter for file kind
- Generating fully qualified tags automatically from scope information
- Multi-line pattern match
- Advanced pattern matching with multiple regex tables
- Scheduling a guest parser with
_guest
regex flag - Defining a subparser
- Making tags of foreign languages
- Translating an option file into C source code (optlib2c)
- Optscript, a programming language for extending optlib parsers
- Extending ctags with a parser written in C
- Testing ctags
- Testing a parser
- Testing readtags
- Request for extending a parser (or Reporting a bug of parser)
- Contributions
- How to release a new version
- Relationship between other projects
- Who we are