New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@xrefitem with empty heading string (Origin: bugzilla #719639) #5369

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status VERIFIED severity enhancement in component build for ---
Reported in version 1.8.5 on platform Other
Assigned to: Dimitri van Heesch

On 2013-12-01 13:38:03 +0000, albert wrote:

In case parameter "(heading)" of the @xrefitem is the empty string no heading is generated. This can be useful when used in combination with the \page command e.g.

/** @page my_errors My Errors

  • @brief Errors page
  • Errors page contents.

/** \error ERROR 101: in case a file can not be opened.
Check about file system read/write access. */

/** \error ERROR 102: in case a file can not be closed.
Check about file system read/write access. */

with \error defined as
ALIASES += "error=\xrefitem my_errors "" """

Currently when the "(heading)" is left empty a click-able colon remains in the HTML output.

On 2013-12-01 13:46:07 +0000, albert wrote:

If just pushed a fix to git (pull request 61)

On 2013-12-07 22:26:35 +0000, Dimitri van Heesch wrote:

Thanks, I've just merged the pull request.

On 2013-12-24 18:59:42 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

On 2013-12-29 18:09:25 +0000, albert wrote:

Verified. In version 1.8.6 the problem of the clickable colon is solved.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment