From: martin rudalics <rudalics@gmx.at>
To: era+emacsbugs@iki.fi, 4030@emacsbugs.donarmstrong.com
Cc: submit@emacsbugs.donarmstrong.com
Subject: bug#4030: forward-sexp parses character literal ?; as comment
Date: Tue, 04 Aug 2009 14:43:44 +0200 [thread overview]
Message-ID: <4A782D00.4040808@gmx.at> (raw)
In-Reply-To: <1249387642.18128.1328220453@webmail.messagingengine.com>
> It seems that forward-sexp (and its underlying C implementation) does
> not cope correctly with a character literal semicolon, seeing instead
> (effectively) end of line.
>
> In the *scratch* buffer if you write (insert ?;) you can evaluate this
> Lisp code and it behaves as intended (inserts a semicolon in the current
> buffer) but doing M-x forward-sexp just before the expression results in
> an "Unbalanced parentheses" error.
A similar thing happens with (insert ?") so why don't you escape such a
character by writing (insert ?\;) instead? From the Elisp manual:
You can use the same syntax for punctuation characters, but it is
often a good idea to add a `\' so that the Emacs commands for editing
Lisp code don't get confused. For example, `?\(' is the way to write
the open-paren character. If the character is `\', you _must_ use a
second `\' to quote it: `?\\'.
martin
next prev parent reply other threads:[~2009-08-04 12:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:07 bug#4030: forward-sexp parses character literal ?; as comment era+emacsbugs
2009-08-04 12:43 ` martin rudalics [this message]
2009-08-05 8:17 ` era+emacsbugs
2009-08-05 14:29 ` martin rudalics
2009-08-06 8:55 ` era+emacsbugs
2009-08-06 18:51 ` Stefan Monnier
2009-08-07 13:01 ` martin rudalics
2009-08-10 19:59 ` Stefan Monnier
2009-08-11 9:17 ` martin rudalics
2016-06-18 3:47 ` Andrew Hyatt
2016-06-18 4:31 ` Stefan Monnier
2017-05-13 2:55 ` npostavs
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=4A782D00.4040808@gmx.at \
--to=rudalics@gmx.at \
--cc=4030@emacsbugs.donarmstrong.com \
--cc=era+emacsbugs@iki.fi \
--cc=submit@emacsbugs.donarmstrong.com \
/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.