From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Stefan Kangas <stefan@marxist.se>
Cc: 24982@debbugs.gnu.org
Subject: bug#24982: 24.5; way to let Elisp reader ignore unreadable #(...) constructs
Date: Sat, 22 Aug 2020 12:28:32 -0700 (PDT) [thread overview]
Message-ID: <947a8471-8f34-40a9-852c-dc3a0997f9dc@default> (raw)
In-Reply-To: <87tuwuh4mj.fsf@gnus.org>
> The problem is when the thing inside the construct is unreadable, not
> when there's errors (in a syntactically valid form). For instance:
>
> (ignore-errors #0)
>
> In Common Lisp, this is the #| ... |# operator, and it's handy
> occasionally. It's really like a nesting comment thing...
Good point. I was thinking of #(...), but yes,
the situation is more general. It's about #
syntax that's found to be invalid, but for cases
where # nevertheless can tell where the sexp
parsing should end (and so can advance point there).
next prev parent reply other threads:[~2020-08-22 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 21:47 bug#24982: 24.5; way to let Elisp reader ignore unreadable #(...) constructs Drew Adams
2018-04-02 19:32 ` Juri Linkov
2018-04-02 20:31 ` Drew Adams
2018-04-02 20:54 ` Juri Linkov
2018-04-02 21:32 ` Drew Adams
2018-04-03 20:06 ` Juri Linkov
2020-08-22 19:13 ` Stefan Kangas
2020-08-22 19:17 ` Lars Ingebrigtsen
2020-08-22 19:28 ` Drew Adams [this message]
2020-08-22 19:53 ` Lars Ingebrigtsen
2020-08-22 22:44 ` Drew Adams
2020-08-22 19:25 ` Drew Adams
2022-02-13 8:46 ` Lars Ingebrigtsen
2022-02-13 17:33 ` bug#24982: [External] : " Drew Adams
2022-02-13 17:53 ` Lars Ingebrigtsen
2022-02-13 18:03 ` Drew Adams
2022-02-14 4:15 ` Richard Stallman
2022-04-30 17:01 ` Lars Ingebrigtsen
2022-04-30 17:26 ` Drew Adams
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=947a8471-8f34-40a9-852c-dc3a0997f9dc@default \
--to=drew.adams@oracle.com \
--cc=24982@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).