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 654871 - Manpages require excessive backslash-escaping
Manpages require excessive backslash-escaping
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.7.4
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2011-07-18 20:48 UTC by Bas Wijnen
Modified: 2018-07-30 10:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bas Wijnen 2011-07-18 20:48:58 UTC
I got incorrect manpages from the code:
..., std::string const &delimiters = std::string (" \t\v\f\a\n\r\0", 8));

Which results in a manpage containing:
std::string(' \\t\\v\\f\\a\\n\\r\\0', 8))

(As an aside, the double quotes have been replaces with single quotes, which is not correct C++)

The problem is that man appearantly evaluates this thing three times before displaying. This means that every backslash must be thrice doubled, leading to 8 backslashes:
' \\\\\\\\t\\\\\\\\v\\\\\\\\f\\\\\\\\a\\\\\\\\n\\\\\\\\r\\\\\\\\0'

This gives the result of a single backslash in the manpage as shown by man and no more warnings from man.

Arguably this is a bug in man. However, given that everybody uses it with the current syntax, I don't think it's realistic to request a parser change for it.
Comment 1 André Klapper 2018-07-30 10:49:32 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!