Install universal-ctags with Homebrew, chocolatey, apt, MacPorts, Nix, pacman, scoop, winget, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• optscript
• readtags

Project history

The Universal Ctags README states that Exuberant Ctags, maintained by Darren Hiebert, improved traditional ctags with multi-language support, user-defined regex languages, and Emacs TAGS output, but that project activity stalled. Reza Jelveh initially created a personal GitHub fork, and growing participation led to a dedicated Universal Ctags project.

Universal Ctags set out to continue Exuberant Ctags in a shared working space. It added and improved language parsers, extended optlib for defining parsers, developed experimental interactive mode, and documented incompatibilities where the maintained implementation deliberately diverges from Exuberant behavior.

Adoption history

ctags files are a long-standing contract between command-line indexers and editors. Universal Ctags' adoption grew because Vim, Emacs, source browsers, IDE plugins, static documentation tools, and cross-reference engines still benefit from a fast, language-aware tags generator.

The official docs track related consumers and neighboring projects, including GNU Global, GNU Source-highlight, OpenGrok, Pygments, Geany, Anjuta, and Vim Tagbar. The input also shows broad packaging under names such as universal-ctags or ctags across Homebrew, Debian, Ubuntu, Fedora, Arch, Nix, MacPorts, Windows package managers, and others.

How it is used

The basic package workflow is simple: run ctags over a source tree and point an editor or tool at the generated tags file. Advanced users customize language parsing, emitted fields, extras, pseudo-tags, and per-directory option files.

Universal Ctags changed important configuration defaults compared with Exuberant Ctags. Its README calls out that it does not load ~/.ctags and ./.ctags at startup, preferring ~/.ctags.d/*.ctags and ./.ctags.d/*.ctags; that matters directly to package upgrades and dotfile migrations.

Why package nerds care

Universal Ctags is package-nerd significant because it is a tiny binary with a huge blast radius: editors, code browsers, documentation systems, and source-search tools may all consume its output. Keeping it maintained keeps decades of ctags workflows viable for modern languages.

It is also a clean example of the package-manager replacement pattern: distributions can switch users from an unmaintained upstream to a maintained fork while preserving the old command name and most file-format compatibility.

Timeline

• Pre-2010s: Exuberant Ctags became the widely used multi-language ctags implementation.
• 2010s: Exuberant Ctags activity stalled; Reza Jelveh created a GitHub fork.
• 2010s: The fork became the Universal Ctags project as more contributors joined.
• 2017: Windows daily builds documented the change away from loading legacy ~/.ctags-style files.
• 2019: Windows daily builds documented default slash path separators and UTF-8 code page behavior on modern Windows.

Related projects

• Universal Ctags descends from Exuberant Ctags and traditional Unix ctags. Official docs also discuss Geany's derived tagging engine and downstream consumers such as GNU Global, OpenGrok, Pygments, GNU Source-highlight, Anjuta, and Tagbar.
• Its companion commands and documentation include readtags, optscript, ctags-client-tools, ctags-optlib, and man pages covering tags file formats and incompatibilities.

Sources

• https://docs.ctags.io/en/latest/contributions.html
• https://docs.ctags.io/en/latest/man/ctags-client-tools.7.html
• https://docs.ctags.io/en/latest/other-projects.html
• https://github.com/universal-ctags/ctags
• https://github.com/universal-ctags/ctags-win32
• source_facts.package-manager