From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: 8935@debbugs.gnu.org
Subject: bug#8935: 24.0.50; `substitute-command-keys' doc
Date: Fri, 15 Jul 2011 09:00:08 -0700 [thread overview]
Message-ID: <272E8A17AE3C42699357E7293692E7DA@us.oracle.com> (raw)
In-Reply-To: <m262n3sgnm.fsf@igel.home>
> > It has no special effect on special character combinations
> > such as `\[' and `\='. If you really want to say something
> > about escaping `\' as the next character then I suppose you
> > could: "In particular, `\=\' produces `\' in the output.
>
> This is wrong, because \ by itself has no special meaning, so
> you don't need to precede it by \=.
It's not wrong. \ by itself has no special meaning, so it need not be escaped
when by itself - agreed.
But \ followed by these particular chars (e.g. `[') does have special meaning
for `substitute-command-keys', so when followed by such a char it does need to
be escaped, if you want `\' in the output.
It is nevertheless the \ and only the \ that is escaped. The escaping code
takes no look past the \ to see what follows it. It is you, the programmer, who
decides whether a particular \ needs escaping, and yes, you do that by looking
at the following char (e.g. `[').
But _you_ do that - that is not part of what `substitute-command-keys' does or
`\=' does.
next prev parent reply other threads:[~2011-07-15 16:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 21:29 bug#8935: 24.0.50; `substitute-command-keys' doc Drew Adams
2011-07-15 14:32 ` Lars Magne Ingebrigtsen
2011-07-15 15:33 ` Andreas Schwab
2011-07-15 16:00 ` Drew Adams [this message]
2011-07-15 16:35 ` Lars Magne Ingebrigtsen
2011-07-15 16:35 ` Lars Magne Ingebrigtsen
2011-07-15 17:23 ` Drew Adams
2011-07-15 17:28 ` Lars Magne Ingebrigtsen
2011-07-15 18:38 ` Andreas Schwab
2011-07-15 19:17 ` Drew Adams
2011-07-15 20:09 ` Andreas Schwab
2011-07-15 19:18 ` Drew Adams
2011-07-15 19:22 ` Lars Magne Ingebrigtsen
2011-07-15 19:25 ` Drew Adams
2011-07-18 13:55 ` Stefan Monnier
2011-07-18 14:27 ` Andreas Schwab
2011-07-18 16:20 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=272E8A17AE3C42699357E7293692E7DA@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8935@debbugs.gnu.org \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).