From: Andreas Schwab <schwab@linux-m68k.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>,
'Chong Yidong' <cyd@gnu.org>,
1169@debbugs.gnu.org
Subject: bug#1169: 23.0.60; (substitute-command-keys "\\{...}") adds extra newline
Date: Wed, 30 May 2012 22:02:26 +0200 [thread overview]
Message-ID: <m2sjeha14d.fsf@igel.home> (raw)
In-Reply-To: <E11CEDAC10CF4480830233A75C119987@us.oracle.com> (Drew Adams's message of "Wed, 30 May 2012 10:36:15 -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.
>
> The `}' character "denotes the end", perfectly.
Which '}' character?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-05-30 20:02 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
2012-05-30 17:36 ` Drew Adams
2012-05-30 20:02 ` Andreas Schwab [this message]
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=m2sjeha14d.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=1169@debbugs.gnu.org \
--cc=cyd@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.