From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 20852@debbugs.gnu.org
Subject: bug#20852: 24.3; update-file-autoloads doesn't accept unescaped parenthesis character literal
Date: Sun, 21 Jun 2015 12:13:53 +0000 [thread overview]
Message-ID: <CAArVCkSWZqKLzxbU8vDJZ-ArO8b32NNnduFftDBh2zBf=-JV2A@mail.gmail.com> (raw)
In-Reply-To: <jwvoakb5r4b.fsf-monnier+emacsbugs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Fr., 19. Juni 2015 um
23:24 Uhr:
> > Create an Elisp file such as
> > (defvar foo ?()
> > and try to run `update-file-autoloads' on it. This will fail with an
> > unbalanced parenthesis error. However, this is valid (albeit
> > discouraged) Elisp code.
>
> Yes: don't do that. Use (defvar foo ?\() instead.
> This same error will appear during interactive editing of that code.
>
>
>
If this is generally unsupported, can we then remove it from the doc and
have the reader print a warning (or reject it altogether)?
[-- Attachment #2: Type: text/html, Size: 913 bytes --]
next prev parent reply other threads:[~2015-06-21 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 19:22 bug#20852: 24.3; update-file-autoloads doesn't accept unescaped parenthesis character literal Philipp Stephani
2015-06-19 21:24 ` Stefan Monnier
2015-06-21 12:13 ` Philipp Stephani [this message]
2015-06-22 1:18 ` Stefan Monnier
2015-06-28 13:12 ` Philipp Stephani
2015-06-30 20:43 ` Philipp Stephani
2015-07-02 15:50 ` Stefan Monnier
[not found] ` <20170501142718.3510-1-phst@google.com>
2017-05-01 17:59 ` bug#20852: [PATCH] Warn about missing backslashes during load Stefan Monnier
2017-05-01 18:41 ` Philipp Stephani
2017-05-06 21:14 ` [PATCH] Make `old-style-backquotes' variable internal Philipp
2017-05-07 2:31 ` Eli Zaretskii
2017-05-07 11:49 ` Philipp
2017-05-13 10:35 ` Philipp Stephani
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='CAArVCkSWZqKLzxbU8vDJZ-ArO8b32NNnduFftDBh2zBf=-JV2A@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=20852@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.