all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 52566@debbugs.gnu.org
Subject: bug#52566: 29.0.50; Wishlist: There should be a print-unreadable-function variable
Date: Sat, 22 Jan 2022 15:14:03 +0100	[thread overview]
Message-ID: <87zgnnj1sk.fsf@gnus.org> (raw)
In-Reply-To: <87zgoz1yml.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 17 Dec 2021 08:25:38 +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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-01-22 14:14 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 [this message]
2022-01-22 14:48   ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgnnj1sk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52566@debbugs.gnu.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 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.