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

[PATCH] Limit generated Doxyfile comments to 80 columns (Origin: bugzilla #583233) #3397

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2009-05-19 17:42:48 +0000, Leandro Lucarella wrote:

Most of the options comments in a Doxyfile generated by Doxygen are limited to 80 columns, which is usually a Good Thing. But a few options has very long descriptions which are not broken in 80 columns lines.

Attached is a patch to fix this issue.

On 2009-05-19 17:44:34 +0000, Leandro Lucarella wrote:

Created attachment 134960
Limit generated Doxyfile comments to 80 columns (against svn r692)

On 2012-11-18 11:07:35 +0000, Dimitri van Heesch wrote:

Changed version 'latest' to '1.8.2-SVN' so I can remove 'latest' as an option as it is a moving target.

On 2013-01-21 19:52:10 +0000, albert wrote:

Created attachment 234042
PATCH: Small length corrections for config.xml

This patch contains small corrections to config.xml. Some lines were just a little bit longer than 80 characters.
(Patch based on svn revision 840).

On 2013-02-23 09:59:39 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2013-05-19 12:36:10 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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