After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608016 - \internal and \subsection
\internal and \subsection
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-01-25 10:20 UTC by Michael Stockman
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Stockman 2010-01-25 10:20:04 UTC
"If the \internal command is put inside a section (see for example \section) all subsection after the command are considered to be internal as well. Only a new section at the same level will be visible again."

I did initially think that the same would apply to \subsection and \subsubsection. If that is indeed the intention then that could be stated a little more clearly, and then there appears to me to be a functional bug in doxygen as well.

If that is not the intention then that too could be made a little bit more clear.
* There would not be anything example about seeing \section.
* "Only a new section at the same level" would be more like "Only a new \section...".
* Then too there appears to be a functional bug in doxygen.


I have a subpage like this:
/** \page config_page Configuration
\section modes_sec Modes

Text...

\subsection mode_startup_ssec Startup mode

Text...

\internal

Internal text...

\section storage_sec Storage organization

Text...

*/

With INTERNAL_DOCS=NO I don't get anything after \internal, neither in HTML nor in LaTeX.
Comment 1 Dimitri van Heesch 2010-02-20 16:43:41 UTC
> I did initially think that the same would apply to \subsection and
> \subsubsection. If that is indeed the intention then that could be stated a
> little more clearly, and then there appears to me to be a functional bug in
> doxygen as well.

This was the intention. The implementation is indeed not correct and will be fixed in the next release.
Comment 2 Dimitri van Heesch 2010-02-21 12:57:32 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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.