GNU bug report logs - #24982
24.5; way to let Elisp reader ignore unreadable #(...) constructs

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Mon, 21 Nov 2016 21:49:01 UTC

Severity: wishlist

Tags: wontfix

Found in version 24.5

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 24982 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 24982 <at> debbugs.gnu.org
Subject: Re: bug#24982: 24.5;
 way to let Elisp reader ignore unreadable #(...) constructs
Date: Tue, 03 Apr 2018 23:06:24 +0300
>> >> > 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.
>> >>
>> >> There is such macro called ‘ignore-errors’.
>> >
>> > No.  That ignores all errors.
>> >
>> > Is there an error handler that covers all and only #(...) read errors?
>                                               ^^^^^^^^
>> Then you can use something like
>>   (condition-case err
>>       (read (current-buffer))
>>     (invalid-read-syntax err))
>> that for example for unreadable #<marker ...> returns
>>   (invalid-read-syntax "#")
>
> And (read ")((") gives (invalid-read-syntax ")").
> So it's not specific to unreadable #(...) or #....

You can also use the position in the source buffer
to scan text near the error where reading failed.




This bug report was last modified 3 years and 81 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.