From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: 24982@debbugs.gnu.org
Subject: bug#24982: 24.5; way to let Elisp reader ignore unreadable #(...) constructs
Date: Sat, 22 Aug 2020 15:13:31 -0400 [thread overview]
Message-ID: <CADwFkmm8n9KKASi1bToXd-zASKb3C_Xx_itaWYVDfhKSnJ_EVg@mail.gmail.com> (raw)
In-Reply-To: <b5a0fa75-36ea-43f9-b1e6-ab0f2d974669@default> (Drew Adams's message of "Mon, 21 Nov 2016 13:47:45 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> Enhancement request:
>
> Provide a Boolean variable or a wrapper macro that has the effect of not
> raising an error but just skipping over any unreadable #(...) construct.
>
> (I really wish this were available for older Emacs versions. Those are
> the ones that barf on #(...) constructs that are supported in later
> versions.
What's the use-case here? Why can't you use `ignore-errors'?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-22 19:13 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 [this message]
2020-08-22 19:17 ` Lars Ingebrigtsen
2020-08-22 19:28 ` Drew Adams
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=CADwFkmm8n9KKASi1bToXd-zASKb3C_Xx_itaWYVDfhKSnJ_EVg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=24982@debbugs.gnu.org \
--cc=drew.adams@oracle.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).