From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: `unreadablep'
Date: Thu, 16 Dec 2021 10:03:20 +0200 [thread overview]
Message-ID: <8335mtht87.fsf@gnu.org> (raw)
In-Reply-To: <8735mtje0u.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 16 Dec 2021 06:48:49 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org, Po Lu <luangruo@yahoo.com>, Eli Zaretskii
> <eliz@gnu.org>
> Date: Thu, 16 Dec 2021 06:48:49 +0100
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > My memory suggests the plan was to add something like
> > a `print-unreadable-function` that gets called with the offending
> > object. It could then print it any which way it wants, or signal an
> > error or ...
>
> Then it seems like most everybody's who's weighed in is in favour of
> that solution, but perhaps Eli has an opinion. Eli?
It's fine by me, thanks.
next prev parent reply other threads:[~2021-12-16 8:03 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 ` `unreadablep' Ihor Radchenko
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 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335mtht87.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.