masatake
commented
3 months ago I also wanted the feature to support multiple tag files.
Supporting multiple tags files in readtags is not so hard (but not easy enough to implement in a week.).
Each tags file has pseudo tag entries at the beginning:
$ head tags
!_TAG_EXTRA_DESCRIPTION anonymous /Include tags for non-named objects like lambda/
!_TAG_EXTRA_DESCRIPTION fileScope /Include tags of file scope/
!_TAG_EXTRA_DESCRIPTION pseudo /Include pseudo tags/
!_TAG_EXTRA_DESCRIPTION subparser /Include tags generated by subparsers/
!_TAG_FIELD_DESCRIPTION epoch /the last modified time of the input file (only for F\/file kind tag)/
!_TAG_FIELD_DESCRIPTION file /File-restricted scoping/
!_TAG_FIELD_DESCRIPTION input /input file/
!_TAG_FIELD_DESCRIPTION name /tag name/
!_TAG_FIELD_DESCRIPTION pattern /pattern/
!_TAG_FIELD_DESCRIPTION typeref /Type and name of a variable or typedef/They describe how the tags file is generated. readtags utilizes these pseudo-tag entries effectively.
For adding multiple tags files support to readtags, what we have to do:
- write code verifying the consistency of pseudo tag entries in the files,
- make libreadtags and the query engine used in the -Q option thread-safe,
- make the readtags command run functions of libreadtags in multiple threads.
_ADDED after commenting 2. and 3. are for utilizing multiple CPUs. I have only to do 1. to support multiple tag files.
Extending the user interface of the readtags command is simple; if the user specifies -t options multiple times, the command should read all of them after verifying the consistency of pseudo-tag entries.
The alternative user interface introduces a pseudo tag entry for aggregation:
!_READTAGS_INCLUDE_TAGS /somewhere/tags-for-lib1.tags /external tags file/
!_READTAGS_INCLUDE_TAGS /somewhere/tags-for-lib2.tags /external tags file/
!_READTAGS_INCLUDE_TAGS /somewhere/tags-for-lib3.tags /external tags file/
...I only know the partial aspects of the implementation of citre, but I expect the second approach (supporting _READTAGS_INCLUDE_TAGS) doesn't require citre much change to support multiple tags files.
AmaiKinono
First my use case: I have ARM embedded projects that have
I would like to use ctags for the tags files.
I usually am in the project's code, but I want code completion and looking up definitions and such with candidates, that are in the libraries. I figured when I am in a project and I do
M-x citre-create-tags-fileI can just add the paths to the libraries sources in that window that pops up and it creates a tags file for the project with all the libraries tags in it. This works, but I get a tags file that is >40MB. And I have many projects, so I would have to create tags files for each of them that are >40mb each. So what I would like to have instead is a separate tags file for each project with only the projects tags and one for the libraries. (or one for each library, I don't care about that) readtags would then look up a tag in the projects tags file and when it can't find it there it would look in the other files.gtags has the environment variable GTAGSLIBPATH for that. I set it up to point into the libraries sources, create tags files with gtags for them and the rest is on gtags. But how could I set this up for ctags instead? All I could find was some commands to give vim (yes I know, the horror!) several tags files, but not how to do this in emacs. Also it would be best to have it in a set-up-once-and-forget-it style instead of doing it for every project again and again.