GNU bug report logs - #8935
24.0.50; `substitute-command-keys' doc

Previous Next

Full log

View this message in rfc822 format

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Andreas Schwab'" <schwab <at> linux-m68k.org>
Cc: 8935 <at> debbugs.gnu.org
Subject: bug#8935: 24.0.50; `substitute-command-keys' doc
Date: Fri, 15 Jul 2011 09:00:08 -0700

> > 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.