Re: `unreadablep'

[Po Lu]

Ihor Radchenko <yantar92@gmail.com> writes:

> Variable would indeed be better. Using variable is more consistent with
> the existing behaviour. prin1 can already be controlled by variables
> like print-level, print-circle, etc
>
> Though the name should probably start with print-. Maybe something like
> print-unreadable (t by default, nil will make prin1 throw an error, and
> 'replace to print the value of print-unreadable-as instead of unreadable
> object).
>
> Yet another option may be not printing anything when print-unreadable is
> t and throwing an error when print-unreadable is 'error, but I am not
> sure if that much customisation is too much.

How about `print-throw-if-printing-unreadably'?