[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master 4895ca16f7: Ensure that we don't call print-unreadable-functi
From: |
Robert Pluim |
Subject: |
Re: master 4895ca16f7: Ensure that we don't call print-unreadable-function from " prin1" |
Date: |
Thu, 28 Jul 2022 12:28:17 +0200 |
>>>>> On Thu, 28 Jul 2022 06:24:09 -0400 (EDT), Lars Ingebrigtsen
>>>>> <larsi@gnus.org> said:
Lars> branch: master
Lars> commit 4895ca16f76aa0ec044212a2b96ef8646cf4d0ed
Lars> Author: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Commit: Lars Ingebrigtsen <larsi@gnus.org>
Lars> Ensure that we don't call print-unreadable-function from " prin1"
Lars> * src/print.c (PRINTPREPARE): Bind the current buffer so that we
Lars> can retrieve it later.
Lars> (print_vectorlike): Use it (bug#56773).
Lars> (syms_of_print): New internal `print--unreadable-callback-buffer'
Lars> variable.
If itʼs truly internal we should `unintern' it, no?
Robert
--
- Re: master 4895ca16f7: Ensure that we don't call print-unreadable-function from " prin1",
Robert Pluim <=