From: Chong Yidong <cyd@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 1169@debbugs.gnu.org
Subject: bug#1169: 23.0.60; (substitute-command-keys "\\{...}") adds extra newline
Date: Thu, 31 May 2012 00:40:57 +0800 [thread overview]
Message-ID: <878vg9tyee.fsf@gnu.org> (raw)
In-Reply-To: <B506D5A4D01E4F05A3303D510E9586E6@us.oracle.com> (Drew Adams's message of "Wed, 30 May 2012 07:44:34 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> Huh? Two newlines is the wrong thing. It is the point of this bug
> report.
>
> If some other fix is needed than the one that you made, fine. Just
> DTRT. Sounds like `help-make-xrefs' needs to be fixed - dunno.
Two newlines does not seem obviously wrong to me. It is a way of
denoting the end of the key summary, just like the "key" and "binding"
column headers that are also inserted to denote the start. We could
probably do something fancy like using a text property to mark the
extent of the key summary, but that seems like overengineering, and
anyway it might break third-party code that relies on the old behavior.
Feel free to submit a patch for consideration, if you care a lot about
replacing those two newlines, though.
next prev parent reply other threads:[~2012-05-30 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:45 bug#1169: 23.0.60; (substitute-command-keys "\\{...}") adds extra newline Drew Adams
2011-07-07 17:21 ` Lars Magne Ingebrigtsen
2011-07-07 17:25 ` Drew Adams
2011-07-07 17:32 ` Lars Magne Ingebrigtsen
2011-07-07 17:50 ` Drew Adams
2011-07-07 20:06 ` Juanma Barranquero
2012-05-29 17:44 ` Johan Bockgård
2012-05-29 19:06 ` Drew Adams
2012-05-30 14:10 ` Chong Yidong
2012-05-30 14:44 ` Drew Adams
2012-05-30 16:40 ` Chong Yidong [this message]
2012-05-30 17:36 ` Drew Adams
2012-05-30 20:02 ` Andreas Schwab
2012-05-30 20:21 ` Drew Adams
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=878vg9tyee.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=1169@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
/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.