albert-github

As far as I can tell te problems as mentioned in this issue and the testing of this issue as noted in https://github.com/doxygen/doxygen/issues/10976#issuecomment-2848487523are solved / explained how it works. I...

From the documentation I get: ``` WARN_NO_PARAMDOC This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that are documented, but have no documentation for their parameters or return...

Problem I have with the updated question is that it is now a new issue and should either be a new issue or outlined in a comment. The original question...

@doxygen In the function `void MemberDefImpl::warnIfUndocumentedParams() const` (memberdef.cpp)it looks like that in the construct: ``` if (!Config_getBool(EXTRACT_ALL) && Config_getBool(WARN_IF_UNDOCUMENTED) && Config_getBool(WARN_NO_PARAMDOC) && isFunction() && !isDeleted() && !isReference() && !Doxygen::suppressDocWarnings) ```...

To be sure we are talking about the same issue always: - Can you please attach a, small, self contained example (source+configuration file in a, compressed, tar or zip file!)...

I see in the common mark spec indeed the example: ``` Foo *bar baz* ==== ``` where the translation would be: ``` Foo bar baz ``` in doxygen terms the...

I think it is not only about the length but most of the time also about the, bad, formulation of the section title. The section title you mention: > I...

From images it is hard / not possible to get the proper file to see what causes the problem. So: - Can you please attach a, small, self contained example...

I did some further bisection on the problem and it looks like: ab483cd3ba39614dacc4f4e3901ac1cf76d413ca is the first bad commit ``` commit ab483cd3ba39614dacc4f4e3901ac1cf76d413ca Date: Mon Jan 11 13:56:35 2021 +0100 bug_560861 Class...

I see another problem in the `man` version as well with nested `` tags. when having: ``` The format will be used to verify and load all input files into...