albert-github

- BUG \c verbatim with /// and no inline \verbatim I think the relevant part of the issue: ``` - test \c verbatin \e inline → \b problem not \e...

- BUG snippet in FRONT of \e block_id reference SAME page Interesting case, is a corner case probably never thought about. The solution I see here is to use the...

- BUG \page with string `__parser__` I split the problem and have for this part: ``` /** \mainpage bug # BUG \\page with string \_\_parser\_\_ BUG: the format code is...

- BUG \page with string `__parser__` The problem you see is probably in the page that is referenced by the link: ``` /** \page alc-parser alc __parser__ **/ ``` which...

@aotto1968 seen the complexity, the misunderstandings, the overview, the classification etc. it is better to split the issue in 5 separate issues. - can you create the 5 issues based...

@aotto1968 do you plan plan to split the issue in sub issues as requested in https://github.com/doxygen/doxygen/issues/11060#issuecomment-2275162912

@duncan-roe with the negative numbers the handling of the initializers is only changed for the one line initializers i.e. one line initializers are also shown just in a "code block"...

@doxygen I know but I made a comment there https://github.com/doxygen/doxygen/issues/11036#issuecomment-2271379309 that is the reason I left it open for the moment.

The matter of taste regarding the one line function macros remains, the `n_pi` example in https://github.com/doxygen/doxygen/issues/11036#issuecomment-2271379309 shows a very simple example but one also could think about an example like:...

Due to a missing settings file it is hard to reproduce the problem. When using a default settings file I can reproduce the `void A::foo()` problem with the doxygen 1.3.6...