From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: How to bind the keyboard 'C-;'
Date: Fri, 16 Mar 2007 10:06:26 -0400 [thread overview]
Message-ID: <jwvhcsls2ta.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.994.1174028547.7795.help-gnu-emacs@gnu.org
> and [?\C-;]
> Can anyone explain why the semicolon does not need to be backslashed
> there?
Well, it kind of does: the `read' function will not need a backslash because
when it sees "?\C-" is knows that what follows can't be a comment (because
"?\C-" on its own is not a valid lexeme).
But emacs-lisp-mode doesn't understand this (because it doesn't use the full
builtin lisp parser), so font-lock and syntax-based navigation (e.g. C-M-f)
will not treat it correctly if the ; is not escaped.
Stefan
prev parent reply other threads:[~2007-03-16 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 23:12 How to bind the keyboard 'C-;' Vols
2007-03-14 0:49 ` John Paul Wallington
2007-03-16 7:00 ` Kevin Rodgers
[not found] ` <mailman.994.1174028547.7795.help-gnu-emacs@gnu.org>
2007-03-16 14:06 ` Stefan Monnier [this message]
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=jwvhcsls2ta.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.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.
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).