Project

General

Profile

Bug #4023

Properly escape newlines and carriage returns in man pages

Added by Josef Sipek over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
manpage - manual pages
Start date:
2013-08-09
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
Gerrit CR:

Description

       file "$1" | grep -Fq executable &&
                 printf "%s is executable.0 "$1"

the "0" should be "\\n"

#1

Updated by Rich Lowe over 7 years ago

  • Subject changed from type in file(1) manpage to typo in file(1) manpage
#2

Updated by Rich Lowe over 7 years ago

ar has the same problem, near "characters to pad these objects".

If you grep our manual pages for '\\n', and exclude those not in verbatim sections, you'll probably find a great many such bugs.

#3

Updated by Bart Coddens over 7 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

Easy fix, webrev coming up

#5

Updated by Robert Mustacchi about 7 years ago

  • Subject changed from typo in file(1) manpage to Properly escape \\n and \\r in man pages
#6

Updated by Robert Mustacchi about 7 years ago

  • Subject changed from Properly escape \\\\n and \\\\r in man pages to Properly escape \\n and \\r in man pages
#7

Updated by Robert Mustacchi about 7 years ago

  • Subject changed from Properly escape \\\\n and \\\\r in man pages to Properly escape '\\n' and '\\r' in man pages
#8

Updated by Robert Mustacchi about 7 years ago

  • Subject changed from Properly escape '\\\\n' and '\\\\r' in man pages to Properly escape newlines and carriage returns in man pages
#9

Updated by Robert Mustacchi about 7 years ago

  • Category set to manpage - manual pages
  • % Done changed from 90 to 100
  • Tags deleted (needs-triage)

Resolved in 98cdf45a92ada981b8c4e22ac69956b4139b1341.

#10

Updated by Robert Mustacchi about 7 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF