Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@b4n approved this pull request.
Apart the small doc changes, LGTM. Limited testing shows it works nicely, including mixed languages in a tags file. Older tags files I had laying around using either Pipe or Tagmanager format still seemed to work as usual. I didn't have any older ctags tags file with the now unsupported header, but adding it to a new one produces the warning yet seems to still work without too much problem.
In doc/geany.txt:
> + +Geany supports loading tag files generated using the ``ctags`` command-line +tool from the universal-ctags project (https://github.com/universal-ctags/ctags). +Even though Geany should work with any ctags file, it is recommended to use +certain fields to give Geany some additional information. The recommended fields +are ``EfiklsZSt``, so to generate symbols for all sources in the my_project +directory one can use:: + + ctags -n --fields=EfiklsZSt -R -o my_project.c.tags my_project + +Additional options may be given to the ``ctags`` tool, for instance, to restrict +the generated tags file to some languages only, use certain tag kinds, etc. + +Note that when the ``l`` field (specifying the programming language) is enabled, +the language of all symbols is set based on the value of this field instead of +the language specified in the extension of the tags file.⬇️ Suggested change
-the language specified in the extension of the tags file. +the language specified in the extension of the tags file. You however still +have to name the file according to the same rules regardless of whether the +language field is used.
or something like that, IIUC what you said somewhere else.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.