Summary
Vim, Emacs, Sublime, and many other editors consume tags files (Exuberant ctags / Universal Ctags format) for jump-to-definition. CodeIndex already has all the symbol/file/line data needed to emit this format, but there is no cdidx export ctags command. Editor users currently have to run universal-ctags separately and lose the benefit of CodeIndex's cross-language consistency.
Where
src/CodeIndex/Cli/ProgramRunner.cs (no export subcommand)src/CodeIndex/Database/DbReader.cs (already has all the symbol data)
Suggested approach
(1) Add cdidx export ctags [--output=tags] that walks Symbols table and emits standard ctags format (name<TAB>file<TAB>pattern). (2) Optionally add --format=etags for Emacs etags format. (3) Document in USER_GUIDE.md editor-integration section.
Summary
Vim, Emacs, Sublime, and many other editors consume
tagsfiles (Exuberant ctags / Universal Ctags format) for jump-to-definition. CodeIndex already has all the symbol/file/line data needed to emit this format, but there is nocdidx export ctagscommand. Editor users currently have to run universal-ctags separately and lose the benefit of CodeIndex's cross-language consistency.Where
src/CodeIndex/Cli/ProgramRunner.cs(no export subcommand)src/CodeIndex/Database/DbReader.cs(already has all the symbol data)Suggested approach
(1) Add
cdidx export ctags [--output=tags]that walksSymbolstable and emits standard ctags format (name<TAB>file<TAB>pattern). (2) Optionally add--format=etagsfor Emacs etags format. (3) Document inUSER_GUIDE.mdeditor-integration section.