unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52566@debbugs.gnu.org
Subject: bug#52566: 29.0.50; Wishlist: There should be a print-unreadable-function variable
Date: Sat, 22 Jan 2022 16:48:44 +0200	[thread overview]
Message-ID: <83ee4zn7w3.fsf@gnu.org> (raw)
In-Reply-To: <87zgnnj1sk.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  22 Jan 2022 15:14:03 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 22 Jan 2022 15:14:03 +0100
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > It should be called from print_vectorlike (and any other places that
> > print unreadable objects, but I'm not sure there are any other places),
> > and should probably have a signature like
> >
> > OBJECT PRINTCHARFUN ESCAPEFLAG
> >
> > If it returns nil, the object should be printed as normal.
> >
> > This can then be used to implement a `readablep' function (that would
> > bind this to a function that signals an error, and then catch that
> > error), and also to possibly make an alternative version of prin1 that
> > returns whether it printed something unprintable.
> 
> This has now been implemented in Emacs 29.  The function interface was
> changed a bit, though.

The doc string of print-unreadable-function and its documentation in
the manual seem to contradict each other.





  reply	other threads:[~2022-01-22 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  7:25 bug#52566: 29.0.50; Wishlist: There should be a print-unreadable-function variable Lars Ingebrigtsen
2022-01-22 14:14 ` Lars Ingebrigtsen
2022-01-22 14:48   ` Eli Zaretskii [this message]
2022-01-22 15:25     ` Lars Ingebrigtsen
2022-01-22 15:36       ` Eli Zaretskii
2022-01-22 15:46         ` Lars Ingebrigtsen
2022-01-22 16:18           ` Eli Zaretskii
2022-01-22 16:21             ` Lars Ingebrigtsen

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=83ee4zn7w3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52566@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).