From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7843@debbugs.gnu.org, Eric Hanchrow <eric.hanchrow@gmail.com>
Subject: bug#7843: 24.0.50; woman leaves \& in man page header
Date: Fri, 09 Sep 2011 03:07:57 -0400 [thread overview]
Message-ID: <m9hb4m8a7m.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87hbcs911x.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 28 Jan 2011 16:21:46 -0500")
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Chong Yidong wrote:
> I've checked in what I think is a correct fix into the trunk.
>
> (I'm hardly an expert in this part of the code, so it's better not to
> put it in the branch in case it turns out to be a wrong fix.)
You jinxed it. ;)
It seems to cause problems. man.1 (attached) renders worse in the
current trunk than in Emacs 23.3. The woman-log buffer has many entries
that do not appear in 23.3:
** Escape ignored: \- -> -
[many times]
** Escape ignored: \f -> f
[many times]
** .. request ignored!
[several times]
** Numeric/register argument error: w'man 'u
An example of a section that renders worse is
The following conventions apply to the SYNOPSIS section and
can be used as a guide in other sections.
fBbold textfR@T{
type exactly as shown.
T}
In 23.3, "bold text" is correctly rendered in bold.
Also the spaces are missing between "man" and the arguments in the
following section:
EXAMPLES
man ls
Display the manual page for the item (program) ls.
[-- Attachment #2: man.1.gz --]
[-- Type: application/octet-stream, Size: 12409 bytes --]
next prev parent reply other threads:[~2011-09-09 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 5:01 bug#7843: 24.0.50; woman leaves \& in man page header Eric Hanchrow
2011-01-28 21:21 ` Chong Yidong
2011-09-09 7:07 ` Glenn Morris [this message]
2011-09-09 7:35 ` Eli Zaretskii
2011-09-09 7:53 ` Andreas Schwab
2011-09-09 8:00 ` Eli Zaretskii
2011-09-18 16:06 ` Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m9hb4m8a7m.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=7843@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=eric.hanchrow@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.