Dimitri van Heesch

@aotto1968 It's not about whether it is a problem, it is about a clear use-case (why is this useful?) and a clear specification (which div/value to add, and how to...

The idea of `SUBGROUPING` is to indicate if a group of members that fall under the same section (e.g. All are. "Public Member Functions") will be grouped together under a...

For me, the problem disappears when `EXTRACT_ALL` is enabled. This should not be needed for the XML output, so it is still a bug (probably there is now a check...

@albert-github Indeed, the `*` should have been there only if the comment block already had leading `*`'s to start with. I'll see what's wrong.

@albert-github Looks like this is related to the fix for https://github.com/doxygen/doxygen/issues/10858. The extra `'\n'` added to the `lineStr` by [this fix](https://github.com/doxygen/doxygen/pull/10861/files) seems to be causing the extra whitespace. If I...

@albert-github I've now moved back to my original fix for #10858, while addressing the issues you noticed at the time. It is a tricky thing to get right, so it...

@albert-github the correct counting of the artificially inserted spaces was the problem. I've committed another fix.

@albert-github I'm still trying to find a more robust and consistent approach to handling the spacing around `@include` and `@snippet`. See the attached commit for a new approach. I now...

@albert-github Seems like the difference between C++ and Fortran is because the comment block starts out as a brief description in Fortran (is this intentional?). I now changed this. The...

@hauslude To rule out thread synchronisation related issues in doxygen, does it make a difference if you set `DOT_NUM_THREADS` to `1`?