Subject: bug#52566: 29.0.50; Wishlist: There should be a print-unreadable-function variable

From: Eli Zaretskii <[email-masked]>
Date: Sat, 22 Jan 2022 17:36:00 +0200

> From: Lars Ingebrigtsen <[email-masked]>
> Cc: [email-masked]
> Date: Sat, 22 Jan 2022 16:25:00 +0100
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> > The doc string of print-unreadable-function and its documentation in
> > the manual seem to contradict each other.
> 
> Better now?

Not really.  Or am I missing something?

The doc string says:

  If this function returns nil, the object will be printed as usual.
  If it returns a string, that string will then be printed.  If the
  function returns anything else, the object will not be printed.

But the manual says:

  The function should return either @code{nil} (print nothing), or a
  string (which will be printed), or any other object (which means that
  the object should be printed normally).

The only thing these two agree upon is the case that the function
returns a string.  The other 2 possibilities are described
differently.