Skip to content
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

\internal and \subsection (Origin: bugzilla #608016) #3646

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.6.1 on platform Other
Assigned to: Dimitri van Heesch

On 2010-01-25 10:20:04 +0000, Michael Stockman wrote:

"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.

On 2010-02-20 16:43:41 +0000, Dimitri van Heesch wrote:

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.

On 2010-02-21 12:57:32 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.