From: Ihor Radchenko <yantar92@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: `unreadablep'
Date: Wed, 15 Dec 2021 19:12:08 +0800 [thread overview]
Message-ID: <87a6h2t94n.fsf@localhost> (raw)
In-Reply-To: <87bl1iqh9u.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
>> I am more interested in the ability to print nil (or something else)
>> instead of unreadable objects. My motivations is org-element-cache where
>> we cannot currently store buffer objects because they cannot be restored
>> from printed cache while not increasing the write time significantly (it
>> is bad enough as it is).
>
> Maybe we could have a `print-unreadable-function' that accepts
> `printcharfun' as an argument. That would be very nice indeed.
Do you imply that `print-unreadable-function' should return the new
value to be printed? If so, it is indeed more flexible. Passing the
unreadable value to the function would also be useful (e.g. we can print
buffer file name instead of buffer object).
Best,
Ihor
next prev parent reply other threads:[~2021-12-15 11:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 7:49 `unreadablep' Lars Ingebrigtsen
2021-12-15 8:19 ` `unreadablep' Po Lu
2021-12-15 8:35 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 9:42 ` `unreadablep' Po Lu
2021-12-15 11:16 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 11:25 ` `unreadablep' Po Lu
2021-12-15 12:19 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 12:22 ` `unreadablep' Po Lu
2021-12-15 12:35 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 12:42 ` `unreadablep' Po Lu
2021-12-15 12:44 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 12:46 ` `unreadablep' Po Lu
2021-12-15 12:51 ` `unreadablep' Po Lu
2021-12-15 12:58 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 12:36 ` `unreadablep' Ihor Radchenko
2021-12-15 12:37 ` `unreadablep' Po Lu
2021-12-15 17:00 ` [External] : `unreadablep' Drew Adams
2021-12-15 8:35 ` `unreadablep' Ihor Radchenko
2021-12-15 9:51 ` `unreadablep' Po Lu
2021-12-15 10:20 ` `unreadablep' Ihor Radchenko
2021-12-15 10:21 ` `unreadablep' Ihor Radchenko
2021-12-15 10:21 ` `unreadablep' Po Lu
2021-12-15 10:36 ` `unreadablep' Ihor Radchenko
2021-12-15 10:44 ` `unreadablep' Po Lu
2021-12-15 11:12 ` Ihor Radchenko [this message]
2021-12-15 11:16 ` `unreadablep' Po Lu
2021-12-15 11:39 ` `unreadablep' Ihor Radchenko
2021-12-15 14:12 ` `unreadablep' Stefan Monnier
2021-12-16 5:48 ` `unreadablep' Lars Ingebrigtsen
2021-12-16 8:03 ` `unreadablep' Eli Zaretskii
2021-12-17 7:18 ` `unreadablep' Lars Ingebrigtsen
2021-12-16 15:35 ` `unreadablep' Qiantan Hong
2021-12-17 7:19 ` `unreadablep' Lars Ingebrigtsen
2021-12-15 15:32 ` `unreadablep' Steingold
2021-12-15 16:04 ` `unreadablep' Qiantan Hong
2021-12-15 16:09 ` `unreadablep' Steingold
2021-12-15 20:21 ` `unreadablep' Philipp Stephani
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=87a6h2t94n.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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).