Your message dated Sat, 10 Apr 2010 11:46:19 +0200
with message-id <[email protected]>
and subject line Re: Bug#559928: Syntax error in bash man page: missing
backslash in what is supposed to be a \fP formatting control word
has caused the Debian Bug report #559928,
regarding Syntax error in bash man page: missing backslash in what is supposed
to be a \fP formatting control word
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
559928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559928
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 3.2-4
Severity: minor
The "man" (manual) page for bash has a missing backslash
in what is supposed to be a \fP formatting control word
at or near line 1295 in the gunzip-ed version of the man page
source code. This causes the page to format incorrectly for a
couple of lines. The gzip-ed version is installed as
/usr/share/man/man1/bash.1.gz
After gunzip, the file will normally be called
/usr/share/man/man1/bash.1
The line may be easily found by the following search string in vi:
/[^\\]fP/
which is a regular expression which means "the character string fP
preceded by any character which is not a backslash". In my version
of the bash man page, the string was found on line 1295 as
file where \fB${FUNCNAME[\fP\fI$ifP\fB]}\fP was called
it should be
file where \fB${FUNCNAME[\fP\fI$i\fP\fB]}\fP was called
Of course, after making the change, the file must be gzip-ed again
to be used.
--- End Message ---
--- Begin Message ---
Version: 4.1-1
both seems to be fixed in 4.1-1.
--- End Message ---
