This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

                             Eric S. Raymond
Problems with pylint.1:

Ambiguous or invalid backslash.  This doesn't cause groff a problem.
but it confuses doclifter and may confuse older troff implementations.

--- pylint.1-unpatched  2018-05-18 08:21:03.576466143 -0400
+++ pylint.1    2018-05-18 08:21:03.392467392 -0400
@@ -231,7 +231,7 @@
 .IP "--max-line-length=<int>"
 Maximum number of characters on a single line. [current: 100]
 .IP "--ignore-long-lines=<regexp>"
-Regexp for a line that is allowed to be longer than the limit. [current: 
^\s*(# )?<?https?://\S+>?$]
+Regexp for a line that is allowed to be longer than the limit. [current: 
^\es*(# )?<?https?://\eS+>?$]
 .IP "--single-line-if-stmt=<y_or_n>"
 Allow the body of an if to be on the same line as the test if there is no 
else. [current: no]
 .IP "--no-space-check=NO_SPACE_CHECK"
code-quality mailing list

Reply via email to