OK, made the changes. Apparently it was easier to make this change than I thought; I went the excessively convoluted way :/ (it was my first time!). Tested and it works. Thanks!
> There are many other languages that don't fit the "classical programming language" pattern - for them, you can make the assignments almost arbitrarily. Just avoid `tm_tag_local_var_t` which doesn't show symbols in the sidebar. `tm_tag_undef_t` ignores the symbol completely. You also have to specify these in the groups below so they are shon correctly in the sidebar. OK, noted :) I don't quite understand the use of `tm_tag_local_var_t`. I was thinking that perhaps it was only hidden on the sidebar but still accessible via Ctrl-click, but that doesn't seem to be the case. Anyway, I'll avoid that. And `tm_tag_include_t` too; seems to be the same. (Another question is whether these **should** show up at all, since the use I was giving it was for declaring "internal" signals, and maybe those shouldn't show up, like internal variables of functions.) Overall, my concern is what's the purpose of the different tags. I think it has to do with how they "propagate" to other files and contexts, and that one tm_tag_t behaves differently from another. For example, if I open a file that declares a certain C typedef, or C++ class, and use it in another file, it appears highlighted in light blue. I suppose this has to do with ctags "exporting" the type to other files. I want to be careful not to have this filetype exporting stuff when it doesn't make sense. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/4039#issuecomment-2467008096 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/4039/[email protected]>
