CTags | CTags support for Sublime Text | Code Editor library

There is no simple way to satisfy the goal.

sysreg.h contains assembly language code that makes the C++ indexer of ctags confused. See https://elixir.bootlin.com/linux/v5.4.21/source/arch/arm64/include/asm/sysreg.h#L741

(It would be nice to add a feature to the C++ indexer to skip __ASSEMBLY__ and __ASSEMBLER__ area.)

I found one hacky technique that works only with Universal ctags (https://ctags.io). Your ctags may be Exuberant Ctags. So the technique I will write here may not work with your ctags.

Use --excmd=pattern option like:

Generate compile_commands.json. Parse compile_commands.json, extract all "command": keys, extract all -I include paths from compile commands, interpret them relative to build directory. sort -u the list.

By default, ".h" is associated with C++ parser, not C parser.

Therefore, the command line should be:

There is no reason I can think of for find to split a file name on several lines, except if the name itself has newline characters in it.

If you have such file names, it is probably better to rename these files as I think cscope does not really support file names with newlines in them. At least, I don't think there is a way to list such files in a cscope.files file, even with quoting or any kind of escaping (but if you know how to do, please let us know, such that we can adapt what follows accordingly). So, the best you could do is to let cscope do the search (-R) instead of providing a cscope.files file. If you do so cscope will indeed find and analyse these files, but then, when interacting with cscope you will discover that it gets confused and splits the names anyway...

If you do not have such unusual file names, but there are unwanted newline characters in your cscope.files file, there must be something else that tampers with it.

Anyway, prefer a function. Compared to functions, aliases mainly have drawbacks. With a bash function:

You don't have to define a new language. ctags has Asm parser. Extending the parser is enough. See how I use the backslash characters.

The bigger goal here is to cross-check parameter names defined in header files with the ones used in the actual implementation.

For that, you can use clang-tidy with https://clang.llvm.org/extra/clang-tidy/checks/readability-inconsistent-declaration-parameter-name.html

Ctags is an external program that is not part of Vim. It can't be removed from Vim because it isn't there in the first place.

Vim's various ctags-related commands can't be removed either. If you want to map to something else then there is nothing stopping you.

This normal mode mapping, for example, will delete the current word when you press , effectively overriding the original meaning of :