[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `unreadablep'
From: |
Ihor Radchenko |
Subject: |
Re: `unreadablep' |
Date: |
Wed, 15 Dec 2021 20:36:04 +0800 |
Po Lu <luangruo@yahoo.com> writes:
> The idea is that `print-unreadable-function' is called _with_ the object
> and the printcharfun (and possibly some prin1 state, but I haven't
> thought of the details yet) when prin1 encounters an unreadable object.
What about just calling with the object and then proceeding as usual
inside prin1, but using the return value of print-unreadable-function in
place of the old unreadable value?
Best,
Ihor
- `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep',
Ihor Radchenko <=
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- RE: [External] : Re: `unreadablep', Drew Adams, 2021/12/15
Re: `unreadablep', Ihor Radchenko, 2021/12/15