Masatake YAMATO

When I proposed #3425 after getting the pull request #3424. Though the original commit of #3424 was lost by force-pushing. However, as far as I can remember, the original #3424...

Sorry to be late. This issue is so complex that I feel like running away. > OK. The only thing is that if text is set on any test file,...

I have not read this issue well yet. Here is .ctags I wrote ago: ``` # # containerfile.ctags --- regex parser for Containerfile and Dockerfile # # Copyright (c) 2023,...

The main task of ctags is to extract names newly introduced in a target file. ctags extracts such names as *definition tags*. Though we have extended the task to extract...

I don't understand why you want to show all the commands. Ctags is not a general navigation tool. It focuses on definitions. We need a list of all commands that...

``` # # containerfile.ctags --- regex parser for Containerfile and Dockerfile # # Copyright (c) 2023, 2024, Red Hat, Inc. # Copyright (c) 2023, 2024, Masatake YAMATO # # Author:...

Regarding languages for Documentation, we violate the principle of "making a tag for definition." However, about Cotainerfile/Dockerfile, I want to uphold the principle. If I introduce a parser for the...

NO. However, I have wanted to implement such a feature for years. `-r` (and `--semantic-recurse`, or `-S`) options are reserved. See https://github.com/universal-ctags/ctags/issues/2428

It's inefficient but works. ``` [yamato@dev64 ctags-github]$ cat foo.c cat foo.c #include int main(void) { return 0; } [yamato@dev64 ctags-github]$ bash ./srec-ctags -o - foo.c bash ./srec-ctags -o - foo.c...

I answered the question.