From: Glenn Morris <rgm@gnu.org>
To: Tim Visher <tim.visher@gmail.com>
Cc: 22718@debbugs.gnu.org
Subject: bug#22718: 25.0.50; sexp parser error when 'vector' forms are in the docstring
Date: Wed, 17 Feb 2016 13:33:14 -0500 [thread overview]
Message-ID: <l9fuwr89w5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m11tjt5xqx.fsf@timvisher-rjmetrics.local.i-did-not-set--mail-host-address--so-tickle-me> (Tim Visher's message of "Thu, 09 Apr 2015 07:47:50 -0400")
It's our old friend, unescaped paren in column 0.
You can write \[, or change open-paren-in-column-0-is-defun-start.
next prev parent reply other threads:[~2016-02-17 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 11:47 bug#22718: 25.0.50; sexp parser error when 'vector' forms are in the docstring Tim Visher
2016-02-17 18:33 ` Glenn Morris [this message]
2016-02-17 18:51 ` Tim Visher
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=l9fuwr89w5.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=22718@debbugs.gnu.org \
--cc=tim.visher@gmail.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 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).